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

[Andrew Morton]

Andrea Arcangeli <andrea@xxxxxxx> wrote:
>
> > > The main thing you didn't mention is the overhead in the per-cpu data
>  > > structures, that alone generates an overhead of several dozen mbytes
>  > > only in the page allocator, without accounting the slab caches,
>  > > pagetable caches etc.. putting an high limit to the per-cpu caches
>  > > should make a 32-way 32G work fine with 3:1 too though. 8-way is
>  > > fine with 32G currently.
>  > 
>  > Humpf. Do you have a hard figure on how much it actually is per cpu?
> 
>  not a definitive one, but it's sure more than 2m per cpu, could be 3m
>  per cpu.

It'll average out to 68 pages per cpu.  (4 in ZONE_DMA, 64 in ZONE_NORMAL).

That's eight megs on 32-way.  Maybe it can be trimmed back a bit, but on
32-way you probably want the locking amortisation more than the 8 megs.

The settings we have in there are still pretty much guesswork.  I don't
think anyone has done any serious tuning on them.  Any differences are
likely to be small.


-
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/