Re: RFC: CONFIG_PAGE_SHIFT (aka software PAGE_SIZE)

Rene Herman
2007-07-18T16:35:42Z

On 07/18/2007 03:32 PM, William Lee Irwin III wrote:

> On Tue, Jul 17, 2007 at 09:33:08PM +0200, Andrea Arcangeli wrote:

>> kmalloced 4k naturally aligned object into userland). I wouldn't call
>> it tail packing, it's more a fine-granular pagecache with the already
>> available kmalloc granularities. That will maximize pagecache
>> utilization with read syscall for hg/git compared to current 2.6.22
>> plus memory will be allocated faster in 64k chunks etc... Ideally it
>> should be possible to disable the finer-granular-kmalloc-pagecache on
>> the big irons with lots of memory and only working with big files.
>
> In any event, that is a sound strategy for mitigating internal
> fragmentation of pagecache, though internal fragmentation of anonymous
> memory has more severe consequences and is less easily mitigated.

I suppose low/highmem is an issue on x86? I was reading the tail packing
paper Dave posted a link to earlier:

http://kernel.org/pub/linux/kernel/people/shaggy/OLS-2006/kleikamp.pdf

It says that highmem is not an issue due to no such thing as highmem even
existing on the machines with support for larger hard pagesizes, but this
wouldn't hold for soft pages. Sort of went "damn" in an x86 context upon
reading that.

Rene.