From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nishanth Aravamudan <nacc@us.ibm.com>,
wli@holomorphy.com, anton@samba.org, clameter@sgi.com,
agl@us.ibm.com, linux-mm@kvack.org
Subject: Re: [RFC][PATCH 2/3] hugetlb: numafy several functions
Date: Fri, 25 May 2007 17:47:39 -0400 [thread overview]
Message-ID: <1180129659.21879.52.camel@localhost> (raw)
In-Reply-To: <20070525143908.dfcc0060.akpm@linux-foundation.org>
On Fri, 2007-05-25 at 14:39 -0700, Andrew Morton wrote:
> On Fri, 25 May 2007 16:55:59 -0400 Lee Schermerhorn <Lee.Schermerhorn@hp.com> wrote:
>
> > On Fri, 2007-05-25 at 12:43 -0700, Nishanth Aravamudan wrote:
> > > Andrew,
> > >
> > <snip>
> > > >
> > > > Yeah, if folks like the interface and are satisfied with it working,
> > > > I'll rebase onto -mm for Andrew's sanity.
> > >
> > > Would you like me to rebase onto 2.6.22-rc2-mm1? I think this is a very
> > > useful feature for NUMA systems that may have an unequal distribution of
> > > memory and don't like the hugepage allocations provided by the global
> > > sysctl.
> > >
> > > If I recall right, the collisions with Lee's hugetlb.c changes were
> > > pretty small, so it shouldn't be any trouble at all.
> >
> > Nish:
> >
> > Unless I missed your post, I think Andrew is waiting to hear from you on
> > the results of your testing of the 22-rc2 based v4 patch before merging
> > the huge page allocation fix.
> >
>
> I am in my common state of lost-the-plot on this patchset.
I was referring to the patch that Anton Blanchard started, and I
reworked that distributes huge pages evenly over populated nodes in the
presence of nodes with no memory in the zone from which HUGEPAGES are
allocated. You had asked [off list, last week, 17may] whether we're
still waiting for test results, to which I replied, "yes".
Later, Nish asked me for a version of the patch rebased against 22-rc2
because he was having difficulty building 22-rc*-mm* on his platform.
In this exchange, Nish is referring to his patch to allow explicit, per
node, specification of nr_hugepages via a sysfs attribute.
>
> Once all the issues are believed to be settled, please send fresh shiny new
> patches against latest -linus or, if there is colliding stuff in -mm,
> against latest -mm.
Will do.
Lee
--
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>
prev parent reply other threads:[~2007-05-25 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 23:30 [PATCH 1/3] hugetlb: remove unnecessary nid initialization Nishanth Aravamudan
2007-05-16 23:31 ` [RFC][PATCH 2/3] hugetlb: numafy several functions Nishanth Aravamudan
2007-05-16 23:33 ` [RFC][PATCH 3/3] hugetlb: add per-node nr_hugepages sysfs attribute Nishanth Aravamudan
2007-05-23 17:51 ` [RFC][PATCH 2/3] hugetlb: numafy several functions Nishanth Aravamudan
2007-05-23 19:16 ` Lee Schermerhorn
2007-05-23 19:29 ` Nishanth Aravamudan
2007-05-25 19:43 ` Nishanth Aravamudan
2007-05-25 20:55 ` Lee Schermerhorn
2007-05-25 21:10 ` Nishanth Aravamudan
2007-05-25 21:39 ` Andrew Morton
2007-05-25 21:47 ` Lee Schermerhorn [this message]
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=1180129659.21879.52.camel@localhost \
--to=lee.schermerhorn@hp.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=nacc@us.ibm.com \
--cc=wli@holomorphy.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