lkml.org 
[lkml]   [2009]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] Hugepages should be accounted as unevictable pages.
From
Date
On Tue, 2009-06-23 at 14:05 +0900, KOSAKI Motohiro wrote:
> > > > Unevictable: 0 kB
> > > > Mlocked: 0 kB
> > > > HugePages_Total: 20
> > > > HugePages_Free: 20
> > > > HugePages_Rsvd: 0
> > > > HugePages_Surp: 0
> > > >
> > > > After the patch:
> > > >
> > > > Unevictable: 81920 kB
> > > > Mlocked: 0 kB
> > > > HugePages_Total: 20
> > > > HugePages_Free: 20
> > > > HugePages_Rsvd: 0
> > > > HugePages_Surp: 0
> > >
> > > At first, We should clarify the spec of unevictable.
> > > Currently, Unevictable field mean the number of pages in unevictable-lru
> > > and hugepage never insert any lru.
> > >
> > > I think this patch will change this rule.
> >
> > I agree, and that's why I added a comment to the documentation file to
> > that effect. If you think its not explicit or doesn't explain what its
> > supposed to we can add something more there.
> >
> > IMO, the proc output should give the total number of unevictable pages
> > in the system and, since hugepages are also in fact unevictable so I
> > don't see a reason why they shouldn't be accounted accordingly.
> > What do you think ?
>
> ummm...
>
> I'm not sure this unevictable definition is good idea or not. currently
> hugepage isn't only non-account memory, but also various kernel memory doesn't
> account.
>
> one of drawback is that zone_page_state(UNEVICTABLE) lost to mean #-of-unevictable-pages.
> e.g. following patch is wrong?
>
> fs/proc/meminfo.c meminfo_proc_show()
> ----------------------------
> - K(pages[LRU_UNEVICTABLE]),
> + K(pages[LRU_UNEVICTABLE]) + hstate->nr_huge_pages,
>
>
> Plus, I didn't find any practical benefit in this patch. do you have it?
> or You only want to natural definition?
>
> I don't have any strong oppose reason, but I also don't have any strong
> agree reason.
>
>
> Lee, What do you think?
>

Alok asked me about this off-list. Like you, I have no strong feelings
either way. Before this patch, yes, the Unevictable meminfo item does
correspond to the number of pages on the unevictable lru. However, I
don't know that this is all that useful to an administrator. And, I
don't think we depend on this count anywhere in the code. So, perhaps
having the system "do the math" to add the unevictable huge pages to
this item is more useful. Then, again, as you point out, there is a lot
of kernel memory that is also unevictable that would not be accounted
here.

Lee



\
 
 \ /
  Last update: 2009-06-23 14:29    [W:0.057 / U:0.172 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site