[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1245732411.18339.6.camel@alok-dev1>
Date: Mon, 22 Jun 2009 21:46:51 -0700
From: Alok Kataria <akataria@...are.com>
To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Lee Schermerhorn <Lee.Schermerhorn@...com>,
Dave Hansen <dave@...ux.vnet.ibm.com>,
Mel Gorman <mel@....ul.ie>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH] Hugepages should be accounted as unevictable pages.
On Mon, 2009-06-22 at 20:25 -0700, KOSAKI Motohiro wrote:
> > Looking at the output of /proc/meminfo, a user might get confused in thinking
> > that there are zero unevictable pages, though, in reality their can be
> > hugepages which are inherently unevictable.
> >
> > Though hugepages are not handled by the unevictable lru framework, they are
> > infact unevictable in nature and global statistics counter should reflect that.
> >
> > For instance, I have allocated 20 huge pages on my system, meminfo shows this
> >
> > 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 ?
Thanks,
Alok
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists