From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: paulus@samba.org, linuxppc-dev@ozlabs.org, linux-mm@kvack.org,
anton@au1.ibm.com
Subject: Re: [RFC] hotplug memory remove - walk_memory_resource for ppc64
Date: Thu, 1 Nov 2007 00:46:13 +0900 [thread overview]
Message-ID: <20071101004613.37fee22f.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1193846560.17412.3.camel@dyn9047017100.beaverton.ibm.com>
On Wed, 31 Oct 2007 08:02:40 -0800
Badari Pulavarty <pbadari@us.ibm.com> wrote:
> Paul's concern is, since we didn't need it so far - why we need this
> for hotplug memory remove to work ? It might break API for *unknown*
> applications. Its unfortunate that, hotplug memory add updates
> /proc/iomem. We can deal with it later, as a separate patch.
>
I have no objection to skip /proc/iomem related routine when arch
doesn't need it.
My advice is just "please take care both of hot-add and hot-remove".
If ppc64 people agreed to use arch-specific routine for detect
conventional memory, there is no problem, I think.
Thanks,
-Kame
--
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-10-31 15:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 17:29 [RFC] PPC64 Exporting memory information through /proc/iomem Badari Pulavarty
2007-10-02 20:11 ` Geoff Levand
2007-10-02 20:37 ` Badari Pulavarty
2007-10-02 20:50 ` Geoff Levand
2007-10-02 22:56 ` Paul Mackerras
2007-10-02 23:10 ` Badari Pulavarty
2007-10-03 1:19 ` KAMEZAWA Hiroyuki
2007-10-03 15:35 ` Badari Pulavarty
2007-10-03 16:25 ` KAMEZAWA Hiroyuki
2007-10-03 16:40 ` Badari Pulavarty
2007-10-30 19:19 ` [RFC] hotplug memory remove - walk_memory_resource for ppc64 Badari Pulavarty
2007-10-31 5:28 ` KAMEZAWA Hiroyuki
2007-10-31 5:34 ` KAMEZAWA Hiroyuki
2007-10-31 16:02 ` Badari Pulavarty
2007-10-31 15:46 ` KAMEZAWA Hiroyuki [this message]
2007-10-31 16:48 ` [PATCH 0/3] hotplug memory remove support for PPC64 Badari Pulavarty
2007-10-31 16:10 ` [RFC] hotplug memory remove - walk_memory_resource for ppc64 Badari Pulavarty
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=20071101004613.37fee22f.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=anton@au1.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=pbadari@us.ibm.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