From: Dave Hansen <haveblue@us.ibm.com>
To: Ray Bryant <raybry@sgi.com>
Cc: Hirokazu Takahashi <taka@valinux.co.jp>,
Marcello Tosatti <marcelo.tosatti@cyclades.com>,
linux-mm <linux-mm@kvack.org>
Subject: Re: page migration
Date: Mon, 03 Jan 2005 10:25:33 -0800 [thread overview]
Message-ID: <1104776733.25994.11.camel@localhost> (raw)
In-Reply-To: <41D98556.8050605@sgi.com>
On Mon, 2005-01-03 at 11:48 -0600, Ray Bryant wrote:
> The attached tar file contains a version of the mhp3 patch with the following
> properties:
>
> (1) It splits out the memory migration patches into a separate series file.
> (2) The remaining patches are in the hotplug directory with its own
> series files.
> (3) Rollup patches for the two sets of patches are included.
>
> If one applies the memory_migration patches first, the result compiles and
> links but I admit I have not tested it.
Very cool, thanks for doing this.
> I've been unable to get (either) memory hotplug patch to compile. It won't
> compile for Altix at all, because Altix requires NUMA. I tried it on a
> Pentium machine, but apparently I didn't grab the correct config.
Hmmm. Did you check the configs here?
http://sr71.net/patches/2.6.10/2.6.10-rc2-mm4-mhp3/configs/
> Anyway, the fact that the diff shows the split out patches are equivalent
> to the full mhp3 patch should be good enough.
>
> (The output of the comparison is included as the file reorder.diff).
That's good to know.
> I'd like to see this order of patches become the new order for the memory
> hotplug patch. That way, I won't have to pull the migration patches out
> of the hotplug patch every time a new one comes out (I need the migration
> code, but not the hotplug code for a project I am working on.)
>
> Do you suppose this can be done???
Absolutely. I was simply working them in the order that they were
implemented. But, if we want the migration stuff merged first, I have
absolutely no problem with putting it first in the patch set.
Next time I publish a tree, I'll see what I can do about producing
similar rollups to what you have, with migration broken out from
hotplug.
Thanks again for doing all of this work.
-- Dave
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-01-03 18:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 17:48 Ray Bryant
2005-01-03 18:25 ` Dave Hansen [this message]
2005-01-03 19:04 ` Ray Bryant
2005-01-03 16:24 ` page migration\ Marcelo Tosatti
2005-01-03 17:13 ` Marcelo Tosatti
2005-01-03 20:33 ` Ray Bryant
2005-01-03 18:38 ` Marcelo Tosatti
2005-01-04 15:42 ` Hirokazu Takahashi
2005-01-04 17:34 ` Ray Bryant
2005-01-04 16:11 ` Marcelo Tosatti
2005-01-05 0:08 ` page migration Ray Bryant
2005-01-03 20:30 ` Ray Bryant
2005-01-03 19:37 ` Dave Hansen
2005-01-03 20:15 ` Ray Bryant
2005-01-03 20:17 ` William Lee Irwin III
2005-01-03 20:36 ` Ray Bryant
2005-01-04 14:42 ` Hirokazu Takahashi
2005-01-04 17:30 ` Ray Bryant
2005-01-04 17:40 ` process " Dave Hansen
2005-01-04 18:26 ` Ray Bryant
2005-01-07 16:40 ` page migration patch Ray Bryant
2005-01-10 2:58 ` Dave Hansen
2005-01-07 16:57 ` migration cache, updated Ray Bryant
2005-01-10 10:07 ` Marcelo Tosatti
2005-01-04 22:03 ` page migration Yasunori Goto
2005-01-04 23:58 ` Ray Bryant
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=1104776733.25994.11.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=raybry@sgi.com \
--cc=taka@valinux.co.jp \
/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