From: David Rientjes <rientjes@google.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>,
linux-mm@kvack.org, linux-numa@vger.kernel.org,
Greg Kroah-Hartman <gregkh@suse.de>,
nacc@us.ibm.com, Andi Kleen <andi@firstfloor.org>,
agl@us.ibm.com, apw@canonical.com, eric.whitney@hp.com
Subject: Re: [PATCH 4/4] hugetlb: add per node hstate attributes
Date: Mon, 17 Aug 2009 03:07:45 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0908170259590.6824@chino.kir.corp.google.com> (raw)
In-Reply-To: <1250471441.4472.108.camel@useless.americas.hpqcorp.net>
On Sun, 16 Aug 2009, Lee Schermerhorn wrote:
> Yes. I had planned to ping you and Mel, as I hadn't heard back from you
> about the combined interfaces. I think they mesh fairly well, and the
> per node attributes have the, perhaps desirable, property of ignoring
> any current task mempolicy. But, I know that some folks don't like a
> proliferation of ways to do something.
I agree as a matter of general principle, but I don't think this would be
a good example of it.
I'm struggling to understand exactly how clean the mempolicy-based
approach would be if an application such as a job scheduler wanted to free
hugepages only on specific nodes. Presumably this would require the
application to create a MPOL_BIND mempolicy to those nodes and write to
/proc/sys/vm/nr_hugepages, but that may break existing implementations if
there are no hugepages allocated on the mempolicy's nodes.
> I'll package up the series [I
> need to update the Documentation for the per node attributes] and send
> it out as soon as I can get to it. This week, I'm pretty sure.
>
That's good news, thanks!
next prev parent reply other threads:[~2009-08-17 10:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 18:11 [PATCH 0/4] hugetlb: V1 Per Node Hugepages attributes Lee Schermerhorn
2009-07-29 18:11 ` [PATCH 1/4] hugetlb: rework hstate_next_node_* functions Lee Schermerhorn
2009-07-29 18:11 ` [PATCH 2/4] hugetlb: numafy several functions Lee Schermerhorn
2009-07-29 18:11 ` [PATCH 3/4] hugetlb: add private bit-field to kobject structure Lee Schermerhorn
2009-07-29 18:25 ` Greg KH
2009-07-31 18:59 ` Lee Schermerhorn
2009-07-29 18:12 ` [PATCH 4/4] hugetlb: add per node hstate attributes Lee Schermerhorn
2009-07-30 19:39 ` David Rientjes
2009-07-31 10:36 ` Mel Gorman
2009-07-31 19:10 ` Lee Schermerhorn
2009-08-14 22:38 ` David Rientjes
2009-08-14 23:08 ` Andrew Morton
2009-08-14 23:19 ` Greg KH
2009-08-14 23:53 ` David Rientjes
2009-08-17 1:10 ` Lee Schermerhorn
2009-08-17 10:07 ` David Rientjes [this message]
2009-08-15 10:08 ` Mel Gorman
2009-07-31 19:55 ` David Rientjes
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=alpine.DEB.2.00.0908170259590.6824@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=apw@canonical.com \
--cc=eric.whitney@hp.com \
--cc=gregkh@suse.de \
--cc=linux-mm@kvack.org \
--cc=linux-numa@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=nacc@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).