All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alok Kataria <akataria@vmware.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Rik van Riel <riel@redhat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
	Mel Gorman <mel@csn.ul.ie>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] Hugepages should be accounted as unevictable pages.
Date: Tue, 23 Jun 2009 17:08:34 -0700	[thread overview]
Message-ID: <1245802114.24110.80.camel@alok-dev1> (raw)
In-Reply-To: <1245800490.31856.21.camel@nimitz>


On Tue, 2009-06-23 at 16:41 -0700, Dave Hansen wrote:
> On Tue, 2009-06-23 at 15:23 -0700, Alok Kataria wrote:
> > > Could you just teach the thing to which you are hinting that it also
> > > needs to go look in sysfs for huge page counts?
> > 
> > :) yeah i could do that too...the point is that its a module and the
> > function to get the hugepages count is not exported right now. I could
> > very well add this as an exported symbol and use it from there, but
> > there can be someone who doesn't want symbols to be unnecessarily
> > exported if their is no in-tree modular usage of that symbol. 
> 
> Hmmm.  So what is the module doing?  The ol', "try to get as much memory
> as I possibly can" game? :)
> 
> It sounds like you can get access to the vm statistics from existing
> exported symbols, but the stats don't give you quite the info that you
> need.

>   So, you're trying to change things that you *can* get access to.

:) Not entirely, I thought that UNEVICTABLE by definition should
consider hugepages too. 

> 
> We do export all this stuff to userspace.  We export all of the huge
> page sizes and how many pages are reserved, used, and allocated in each,
> plus the contentious Unevictable.  Could you just do this calculation in
> userspace and pass it into the module with a modparam or sysfs file?

Hmm...lets see, I will look to moving that to userspace or something. 

But irrespective of my need, we must clear the confusion around what
unevictable should actually mean. 

I am biased towards getting hugepages accounted in that :), but what do
others think ? 

Lee, I will let you take a decision on that, if the current semantics
look okay, it would be great if you could update the unevictable_lru
documentation about this being just the number of pages on
unevictable_lru.

Thanks,
Alok
> 
> -- Dave
> 


WARNING: multiple messages have this Message-ID (diff)
From: Alok Kataria <akataria@vmware.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Rik van Riel <riel@redhat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
	Mel Gorman <mel@csn.ul.ie>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] Hugepages should be accounted as unevictable pages.
Date: Tue, 23 Jun 2009 17:08:34 -0700	[thread overview]
Message-ID: <1245802114.24110.80.camel@alok-dev1> (raw)
In-Reply-To: <1245800490.31856.21.camel@nimitz>


On Tue, 2009-06-23 at 16:41 -0700, Dave Hansen wrote:
> On Tue, 2009-06-23 at 15:23 -0700, Alok Kataria wrote:
> > > Could you just teach the thing to which you are hinting that it also
> > > needs to go look in sysfs for huge page counts?
> > 
> > :) yeah i could do that too...the point is that its a module and the
> > function to get the hugepages count is not exported right now. I could
> > very well add this as an exported symbol and use it from there, but
> > there can be someone who doesn't want symbols to be unnecessarily
> > exported if their is no in-tree modular usage of that symbol. 
> 
> Hmmm.  So what is the module doing?  The ol', "try to get as much memory
> as I possibly can" game? :)
> 
> It sounds like you can get access to the vm statistics from existing
> exported symbols, but the stats don't give you quite the info that you
> need.

>   So, you're trying to change things that you *can* get access to.

:) Not entirely, I thought that UNEVICTABLE by definition should
consider hugepages too. 

> 
> We do export all this stuff to userspace.  We export all of the huge
> page sizes and how many pages are reserved, used, and allocated in each,
> plus the contentious Unevictable.  Could you just do this calculation in
> userspace and pass it into the module with a modparam or sysfs file?

Hmm...lets see, I will look to moving that to userspace or something. 

But irrespective of my need, we must clear the confusion around what
unevictable should actually mean. 

I am biased towards getting hugepages accounted in that :), but what do
others think ? 

Lee, I will let you take a decision on that, if the current semantics
look okay, it would be great if you could update the unevictable_lru
documentation about this being just the number of pages on
unevictable_lru.

Thanks,
Alok
> 
> -- Dave
> 

--
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-24  0:08 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 21:25 [PATCH] Hugepages should be accounted as unevictable pages Alok Kataria
2009-06-22 21:25 ` Alok Kataria
2009-06-23  3:25 ` KOSAKI Motohiro
2009-06-23  3:25   ` KOSAKI Motohiro
2009-06-23  4:46   ` Alok Kataria
2009-06-23  4:46     ` Alok Kataria
2009-06-23  5:05     ` KOSAKI Motohiro
2009-06-23  5:05       ` KOSAKI Motohiro
2009-06-23  5:11       ` KAMEZAWA Hiroyuki
2009-06-23  5:11         ` KAMEZAWA Hiroyuki
2009-06-23  5:54         ` Alok Kataria
2009-06-23  5:54           ` Alok Kataria
2009-06-23  6:06           ` KAMEZAWA Hiroyuki
2009-06-23  6:06             ` KAMEZAWA Hiroyuki
2009-06-23 19:28             ` Alok Kataria
2009-06-23 19:28               ` Alok Kataria
2009-06-23 20:30               ` Lee Schermerhorn
2009-06-23 20:30                 ` Lee Schermerhorn
2009-06-23 21:24           ` Rik van Riel
2009-06-23 21:24             ` Rik van Riel
2009-06-23 21:42             ` Alok Kataria
2009-06-23 21:42               ` Alok Kataria
2009-06-23 21:55               ` Rik van Riel
2009-06-23 21:55                 ` Rik van Riel
2009-06-23 22:06                 ` Alok Kataria
2009-06-23 22:06                   ` Alok Kataria
2009-06-23 22:19                   ` Dave Hansen
2009-06-23 22:19                     ` Dave Hansen
2009-06-23 22:55                   ` Rik van Riel
2009-06-23 22:55                     ` Rik van Riel
2009-06-23 23:28                     ` Alok Kataria
2009-06-23 23:28                       ` Alok Kataria
2009-06-23 23:48                       ` Dave Hansen
2009-06-23 23:48                         ` Dave Hansen
2009-06-23 22:15               ` Dave Hansen
2009-06-23 22:15                 ` Dave Hansen
2009-06-23 22:23                 ` Alok Kataria
2009-06-23 22:23                   ` Alok Kataria
2009-06-23 23:41                   ` Dave Hansen
2009-06-23 23:41                     ` Dave Hansen
2009-06-24  0:08                     ` Alok Kataria [this message]
2009-06-24  0:08                       ` Alok Kataria
2009-06-23 12:26       ` Lee Schermerhorn
2009-06-23 12:26         ` Lee Schermerhorn
2009-06-29  9:58 ` Mel Gorman
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=1245802114.24110.80.camel@alok-dev1 \
    --to=akataria@vmware.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=riel@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.