From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: wli@holomorphy.com, agl@us.ibm.com, linux-mm@kvack.org,
Mel Gorman <mel@csn.ul.ie>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/3] hugetlb: numafy several functions
Date: Fri, 8 Feb 2008 09:08:05 -0800 [thread overview]
Message-ID: <20080208170805.GD15903@us.ibm.com> (raw)
In-Reply-To: <1202489237.5346.26.camel@localhost>
On 08.02.2008 [11:47:17 -0500], Lee Schermerhorn wrote:
> On Thu, 2008-02-07 at 10:52 -0800, Nishanth Aravamudan wrote:
> > On 07.02.2008 [13:35:15 -0500], Lee Schermerhorn wrote:
> > > On Wed, 2008-02-06 at 15:15 -0800, Nishanth Aravamudan wrote:
> > > > hugetlb: numafy several functions
> > > >
> > >
> > > <snip>
> > >
> > > Nish: glad to see these surface again. I'll add them [back] into my
> > > tree for testing. I'm at 24-mm1. Can't tell from the messages what
> > > release they're against, but I'll sort that out.
> >
> > They were against -git tip when I rebased ... hrm that would be
> > 551e4fb2465b87de9d4aa1669b27d624435443bb, I believe.
> >
> > > Another thing: I've tended to test these atop Mel Gorman's zonelist
> > > rework and a set of mempolicy cleanups that I'm holding pending
> > > acceptance of Mel's patches. I'll probably do that with these. At
> > > some point we need to sort out with Andrew when or whether Mel's
> > > patches will hit -mm. If so, what order vs yours...
> >
> > I think Mel's patches may be more generally useful than mine (as mine
> > are all keyed on hugepage support). So I would like to see his go first
> > then I can rework mine on top, if that is the order that it ends up
> > happening in.
>
> Nish:
>
> Heads up: Your "smarter retry" patch will need some rework in vmscan.c
> because of the memory controller changes [currently in 24-mm1]. I have
> rebased you patches against 24-mm1, atop Mel's two-zonelist patches and
> my mempolicy cleanup series. I can send you the entire stack or place
> the tarball on a web site, if you're interested.
I can refresh the patchset for -mm, I was just posting based upon
mainline as that was traditionally how I sent patches to Andrew. But in
this case you're right, there are enough collisions with existing -mm
bits that I should rebase.
Thanks for the heads up.
-Nish
--
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>
next prev parent reply other threads:[~2008-02-08 17:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 23:15 Nishanth Aravamudan
2008-02-06 23:18 ` [PATCH 2/3] hugetlb: add per-node nr_hugepages sysfs attribute Nishanth Aravamudan
2008-02-06 23:19 ` [PATCH 3/3] hugetlb: interleave dequeing of huge pages Nishanth Aravamudan
2008-02-06 23:23 ` [UPDATED][PATCH 2/3] hugetlb: add per-node nr_hugepages sysfs attribute Nishanth Aravamudan
2008-02-07 0:03 ` [PATCH " Greg KH
2008-02-07 0:59 ` Nishanth Aravamudan
2008-02-07 18:35 ` [PATCH 1/3] hugetlb: numafy several functions Lee Schermerhorn
2008-02-07 18:52 ` Nishanth Aravamudan
2008-02-08 16:47 ` Lee Schermerhorn
2008-02-08 17:08 ` Nishanth Aravamudan [this message]
2008-02-08 16:37 ` Adam Litke
2008-02-08 16:48 ` Nishanth Aravamudan
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=20080208170805.GD15903@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--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