From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Nishanth Aravamudan <nacc@us.ibm.com>,
wli@holomorphy.com, agl@us.ibm.com, akpm@linux-foundation.org,
linux-mm@kvack.org
Subject: Re: [PATCH 1/4] hugetlb: search harder for memory in alloc_fresh_huge_page()
Date: Fri, 14 Sep 2007 14:20:52 -0400 [thread overview]
Message-ID: <1189794052.5315.48.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0709141041390.15683@schroedinger.engr.sgi.com>
On Fri, 2007-09-14 at 10:43 -0700, Christoph Lameter wrote:
> On Fri, 14 Sep 2007, Nishanth Aravamudan wrote:
>
> > Christoph, Lee, ping? I haven't heard any response on these patches this
> > time around. Would it be acceptable to ask Andrew to pick them up for
> > the next -mm?
>
> I am sorry but there is some churn already going on with other core memory
> management patches. Could we hold this off until the dust settles on those
> and then rebase?
Hi, Nish:
Sorry not to have responded sooner. I have been building your patches
atop my memory policy changes, and I did test them on my platform. The
seem to work. There was one conflict with my memory policy reference
counting fix, but that was easy to resolve. I'd have no problem with
these going in. They probably will conflict with Mel's patches, but
again this should be easy to resolve.
Earlier Christoph said he didn't think Mel's 'one zonelist' series would
make .24. I think that's still under discussion, but if Mel's patches
don't make .24, then I think these should go in. So, I'll go ahead and
ACK them as they are, against 23-rc4-mm1. Still, I think it would a
good idea for you to grab Mel's patches check out the conflicts.
Whether to rebase Mel's atop yours or vice versa is a more difficult
question.
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>
next prev parent reply other threads:[~2007-09-14 18:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 18:21 [PATCH 1/4] hugetlb: search harder for memory in alloc_fresh_huge_page() Nishanth Aravamudan
2007-09-06 18:24 ` [PATCH 2/4] hugetlb: fix pool allocation with empty nodes Nishanth Aravamudan
2007-09-06 18:27 ` [PATCH 3/4] hugetlb: interleave dequeueing of huge pages Nishanth Aravamudan
2007-09-06 18:28 ` [PATCH 4/4] hugetlb: add per-node nr_hugepages sysfs attribute Nishanth Aravamudan
2007-09-14 18:56 ` Christoph Lameter
2007-09-14 18:54 ` [PATCH 3/4] hugetlb: interleave dequeueing of huge pages Christoph Lameter
2007-09-14 19:03 ` Lee Schermerhorn
2007-09-14 19:42 ` Christoph Lameter
2007-09-14 20:09 ` Lee Schermerhorn
2007-09-14 20:16 ` Christoph Lameter
2007-09-14 20:33 ` Lee Schermerhorn
2007-09-24 23:23 ` Nishanth Aravamudan
2007-09-24 23:29 ` Nishanth Aravamudan
2007-09-14 18:53 ` [PATCH 2/4] hugetlb: fix pool allocation with empty nodes Christoph Lameter
2007-09-14 18:57 ` Christoph Lameter
2007-10-02 22:47 ` Nishanth Aravamudan
2007-10-02 23:39 ` Christoph Lameter
2007-09-14 17:26 ` [PATCH 1/4] hugetlb: search harder for memory in alloc_fresh_huge_page() Nishanth Aravamudan
2007-09-14 17:43 ` Christoph Lameter
2007-09-14 18:20 ` Lee Schermerhorn [this message]
2007-09-24 16:22 ` Nishanth Aravamudan
2007-09-24 19:07 ` Christoph Lameter
2007-09-14 18:51 ` Christoph Lameter
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=1189794052.5315.48.camel@localhost \
--to=lee.schermerhorn@hp.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).