Re: 2.6.17-mm1

Andrew,

Andrew Morton wrote:


All 1738 patches:

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17/2.6.17-mm1/patch-list


Is the following patch really needed ?

flatmem-relax-requirement-for-memory-to-start-at-pfn-0.patch

"""
The FLATMEM memory model assumes that memory is in one contigious area
based at pfn 0. If we initialise node 0 to start at any other offset we
will incorrectly map pfn's to the wrong struct page *. The key to the
memory model is the contigious nature of the memory not the location of it.
Relax the requirement for the area to start at 0.
"""

Should ARCH_PFN_OFFSET macro be used instead in order to make pfn/page
convertions work when node 0 start offset do not start at 0 ?

My physical memory start at 0x20000000. So node 0 starts at an offset
different from 0. I setup ARCH_PFN_OFFSET this way

#define ARCH_PFN_OFFSET (0x20000000 << PAGE_SHIFT)

Until now (2.6.17), it works well, but this patch breaks my machine.

If you need more details about my memory mapping, feel free to ask.

Thanks

Franck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
    ... then I'd certainly accept the patch. ... (basically -- if the app cares about memory or cache footprint and is using ... And indeed this cacheline bouncing has shown up on large SGI systems. ... Inserting a ZERO_PAGE for anonymous read faults appears to be a false ...
    (Linux-Kernel)
  • =?iso-8859-15?Q?Re:_[RFC]_BadRAM_still_not_ready_for_inclusion_=3F_(wa?= =?iso-8859-
    ... maybe this patch is just something very special, having many pro's but also con's - so this also could be one reason why it exists for so long outside mainline. ... BadRAM let's you tell the kernel to skip certain regions of ram, ... forever, once it becomes a supported feature, for the benefit of the few ... people who can't or won't replace bad memory. ...
    (Linux-Kernel)
  • [RFC PATCH 0/4]: affinity-on-next-touch
    ... I wrote a patch to support the adaptive data distribution strategy ... certain region of its virtual memory space. ... memory area from read and write accesses and install a signal handler to ... Afterwards, the signal handler clears the page protection ...
    (Linux-Kernel)
  • Re: [patch 00/19] VM pageout scalability improvements
    ... only does it use up CPU time, but it also provokes lock contention ... and can leave large systems under memory presure in a catatonic state. ... This patch series improves VM scalability by: ... segment for reclaimability. ...
    (Linux-Kernel)
  • Re: [patch 02/11] PAT x86: Map only usable memory in x86_64 identity map and kernel text
    ... The main thing required is on the lines of Jesse's patch. ... 32-bit: trim memory not covered by wb mtrrs ... On some machines, buggy BIOSes don't properly setup WB MTRRs to cover all ...
    (Linux-Kernel)