Re: [PATCH] Hugepages should be accounted as unevictable pages.

[Dave Hansen]

On Tue, 2009-06-23 at 15:06 -0700, Alok Kataria wrote:
> What i meant was that you could always calculate the *maximum* amount of
> memory that is going to be used by page table and can also determine the
> % of memory that will be used by slab caches. 

I'm not really sure what you mean by this.  I actually just wrote a
little userspace program the other day that fills virtually all of ram
in with pagetables.  There's no real upper bound on them, unless you're
restricting the amount of mapped space that all the userspace processes
determine.  In the same way, the right usage pattern can give virtually
all the RAM in the system and put it in a single or set of slabs.  It's
probably evictable most of the time, but sometimes large amounts can be
pinned.

> So that ways you should be statically able to tell that no more than 'X'
> amount of memory is going to be locked here.
> Will again like to stress that "X" is not the exact amount that is
> locked here but the one which can be. 
> 
> OTOH, for hugepages and mlocked pages you need to read the exact counts
> as this can change according to user selection. 

I'm a bit lost.  Could we take a step back here and talk about what
you're trying to do in the first place?

-- Dave

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