Re: 2.4.23aa2 (bugfixes and important VM improvements for the high end)

From: Martin J. Bligh (mbligh_at_aracnet.com)
Date: 03/05/04

  • Next message: Timothy Miller: "Re: kernel 'simulator' and wave-form analysis tool?" 
    Date:	Fri, 05 Mar 2004 10:42:55 -0800
To: Andrea Arcangeli <andrea@suse.de>, Ingo Molnar <mingo@elte.hu>

    > It's a nogo for 64G but I would be really pleased to see a workload
    > triggering the zone-normal shortage in 32G, I've never seen any one. And
    > 16G has even more margin.

    The things I've seen consume ZONE_NORMAL (which aren't reclaimable) are:

    1. mem_map (obviously) (64GB = 704MB of mem_map)

    2. Buffer_heads (much improved in 2.6, though not completely gone IIRC)

    3. Pagetables (pte_highmem helps, pmds are existant, but less of a problem,
    10,000 tasks would be 117MB)

    4. Kernel stacks (10,000 tasks would be 78MB - 4K stacks would help obviously)

    5. rmap chains - this is the real killer without objrmap (even 1000 tasks
    sharing a 2GB shmem segment will kill you without large pages).

    6. vmas - wierdo Oracle things before remap_file_pages especially.

    I may have forgotten some, but I think those were the main ones. 10,000 tasks
    is a little heavy, but it's easy to scale the numbers around. I guess my main
    point is that it's often as much to do with the number of tasks as it is
    with just the larger amount of memory - but bigger machines tend to run more
    tasks, so it often goes hand-in-hand.

    Also bear in mind that as memory gets tight, the reclaimable things like
    dcache and icache will get shrunk, which will hurt performance itself too,
    so some of the cost of 4/4 is paid back there too. Without shared pagetables,
    we may need highpte even on 4/4, which kind of sucks (can be 10% or so hit).

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

  • Next message: Timothy Miller: "Re: kernel 'simulator' and wave-form analysis tool?"

    Relevant Pages

    • Re: log-buf-len dynamic
      ... Wake up, dude. ... disk and memory. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: swsusp update: supports discontingmem/highmem
      ... driver is responsible for the memory should handle any required state ... Can't you back out nicely if you don't have enough memory for the image? ... Nigel Cunningham ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Request: I/O request recording
      ... > next reboot. ... > that everything which you will need in the subsequent boot is already in ... > pretty much a waste of time, gaining only 10% or so, from memory. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: lost memory on a 4GB amd64
      ... JM>> reproduce the crash in the simplest possible way, ... JM> AGP aperature settings in your original post ... AGP and PCI I mentioned only as "the bad guys stealing the memory" ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.19-rc1-mm1
      ... It saves quite a bit of memory on even desktop ... workloads as well as avoiding several pagefaults. ... what does RSS actually mean? ...
      (Linux-Kernel)