From: Andrew Morton <akpm@osdl.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, lhms-devel@lists.sourceforge.net,
kmannth@us.ibm.com, y-goto@jp.fujitsu.com
Subject: Re: [PATCH] memory hotadd fixes [1/5] not-aligned memory hotadd handling fix
Date: Wed, 2 Aug 2006 23:38:02 -0700 [thread overview]
Message-ID: <20060802233802.8186eb38.akpm@osdl.org> (raw)
In-Reply-To: <20060803123039.c50feb85.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, 3 Aug 2006 12:30:39 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> After Keith's report of memory hotadd failure, I increased test patterns.
> These patches are a result of new patterns. But I cannot cover all existing
> memory layout in the world, more tests are needed.
> Now, I think my patch can make things better and want this codes to be tested
> in -mm.patche series is consitsts of 5 patches.
I expect the code which these patches touch is completely untested in -mm, so
all we'll get is compile testing and some review.
Given that these patches touch pretty much nothing but the memory hot-add
paths I'd be inclined to fast-track them into 2.6.18. Do you agree that
these patches are sufficiently safe and that the problems that they solve
are sufficiently serious for us to take that approach?
Either way, could I ask that interested parties review this work closely
and promptly?
Thanks.
next prev parent reply other threads:[~2006-08-03 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 3:30 [PATCH] memory hotadd fixes [1/5] not-aligned memory hotadd handling fix KAMEZAWA Hiroyuki
2006-08-03 6:38 ` Andrew Morton [this message]
2006-08-03 7:03 ` KAMEZAWA Hiroyuki
2006-08-03 7:47 ` Yasunori Goto
2006-08-03 18:29 ` keith mannthey
2006-08-04 11:31 ` [Lhms-devel] " Yasunori Goto
2006-08-03 18:13 ` keith mannthey
2006-08-04 0:03 ` keith mannthey
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=20060802233802.8186eb38.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kmannth@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=y-goto@jp.fujitsu.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