linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: akataria@vmware.com
Cc: kosaki.motohiro@jp.fujitsu.com,
	LKML <linux-kernel@vger.kernel.org>,
	Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
	Dave Hansen <dave@linux.vnet.ibm.com>, Mel Gorman <mel@csn.ul.ie>,
	linux-mm@kvack.org
Subject: Re: [PATCH] Hugepages should be accounted as unevictable pages.
Date: Tue, 23 Jun 2009 12:25:44 +0900 (JST)	[thread overview]
Message-ID: <20090623093459.2204.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <1245705941.26649.19.camel@alok-dev1>

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



--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-06-23  3:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 21:25 Alok Kataria
2009-06-23  3:25 ` KOSAKI Motohiro [this message]
2009-06-23  4:46   ` Alok Kataria
2009-06-23  5:05     ` KOSAKI Motohiro
2009-06-23  5:11       ` KAMEZAWA Hiroyuki
2009-06-23  5:54         ` Alok Kataria
2009-06-23  6:06           ` KAMEZAWA Hiroyuki
2009-06-23 19:28             ` Alok Kataria
2009-06-23 20:30               ` Lee Schermerhorn
2009-06-23 21:24           ` Rik van Riel
2009-06-23 21:42             ` Alok Kataria
2009-06-23 21:55               ` Rik van Riel
2009-06-23 22:06                 ` Alok Kataria
2009-06-23 22:19                   ` Dave Hansen
2009-06-23 22:55                   ` Rik van Riel
2009-06-23 23:28                     ` Alok Kataria
2009-06-23 23:48                       ` Dave Hansen
2009-06-23 22:15               ` Dave Hansen
2009-06-23 22:23                 ` Alok Kataria
2009-06-23 23:41                   ` Dave Hansen
2009-06-24  0:08                     ` Alok Kataria
2009-06-23 12:26       ` Lee Schermerhorn
2009-06-29  9:58 ` Mel Gorman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090623093459.2204.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=akataria@vmware.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox