From: Fumihiro Tersawa <terasawa@pst.fujitsu.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
lhms-devel <lhms-devel@lists.sourceforge.net>
Subject: [PATCH] memory hotplug for ia64 (linux-2.6.7) [0/2]
Date: Tue, 20 Jul 2004 18:18:03 +0900 [thread overview]
Message-ID: <20040720181135.12B6.TERASAWA@pst.fujitsu.com> (raw)
Hello,
I updated the memory hotplug patch for an IPF NUMA machines which
posted in April.
The patch is against linux 2.6.7 and works with memory hotplug patch
which Takahashi-san posted on July 14.
Known issues(under investigation):
- remap function may be unable to mmigrate all pages.
- unplug-node function may fail, if page size is other than 4K byte.
- kswapd doesn't terminate when a node is unplugged.
How to apply:
1) First of all, apply patches which Takahashi-san posted on July 14
without [15-16/16].
*If patches of [15-16/16] are applied, compile error will occur
on ia64.
2) Apply this set of patches.
Thank you,
Fumihiro Terasawa.
next reply other threads:[~2004-07-20 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 9:18 Fumihiro Tersawa [this message]
2004-07-22 0:35 ` [PATCH] memory hotplug for ia64 (linux-2.6.7) [0/2] Fumitake ABE
2004-07-27 16:21 ` Fumitake ABE
2004-07-27 16:38 ` [Lhms-devel] " Dave Hansen
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=20040720181135.12B6.TERASAWA@pst.fujitsu.com \
--to=terasawa@pst.fujitsu.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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