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

Alok Kataria
2009-06-23T21:42:27Z

On Tue, 2009-06-23 at 14:24 -0700, Rik van Riel wrote:
> Alok Kataria wrote:
>
> > Both, while working on an module I noticed that there is no way direct
> > way to get any information regarding the total number of unrecliamable
> > (unevictable) pages in the system. While reading through the kernel
> > sources i came across this unevictalbe LRU framework and thought that
> > this should actually work towards providing total unevictalbe pages in
> > the system irrespective of where they reside.
>
> The unevictable count tells you how many _userspace_
> pages are not evictable.
>
> There are countless accounted and unaccounted kernel
> allocations that show up (or not) in other fields in
> /proc/meminfo.
>

> I can see something reasonable on both sides of this
> particular debate. However, even with this patch the
> "unevictable" statistic does not reclaim the total
> number of pages that are unevictable pages from a
> zone, so I am not sure how it helps you achieve your
> goal.
>

Yes but most of the other memory (page table and others) which is
unevictable is actually static in nature. IOW, the amount of this other
kind of kernel unevictable pages can be actually interpolated from the
amount of physical memory on the system.

One thing that i forgot to mention earlier is that, I just need a way to
provide a hint about the total locked memory on the system and it
doesn't need to be the exact number at that point in time.

Lee, due to this reason lazy culling of unevictable pages is fine too.

Hugepages, similar to mlocked pages, are special because the user could
specify how much memory it wants to reserve for this purpose. So that
needs to be taken into consideration i.e it cannot be calculated in some
way.

Thanks,
Alok