From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
linuxppc-dev@ozlabs.org
Subject: Re: [-mm PATCH] updates for hotplug memory remove
Date: Wed, 30 Jan 2008 10:13:05 +0900 [thread overview]
Message-ID: <20080130095002.4CCC.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <1201653101.19684.6.camel@dyn9047017100.beaverton.ibm.com>
> > Have you ever tested hotadd(probe) of the removed memory?
>
> Yes. I did. In my touch testing, I was able to remove memory and add
> it back to the system without any issues.
Oh, really!?
> But again, I didn't force
> the system to use that memory :(
Ah..OK.
>
> > I'm afraid there are some differences of the status between pre hot-add
> > section and the removed section by this patch. I think the mem_section of
> > removed memory should be invalidated at least.
>
> I think its a generic issue. Nothing specific for ppc64. Isn't it ?
Right.
Currently, our machine doesn't have real physical remove feature yet.
(only add).
So, I think testing is not enough around physical removing.
Probably, your box will be first one which can remove physical memory
with Linux. It is good for testing.
If you notice anything, please let me know. :-)
Bye.
--
Yasunori Goto
--
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>
prev parent reply other threads:[~2008-01-30 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 0:31 [-mm PATCH] updates for hotplug memory remove Badari Pulavarty
2008-01-29 0:35 ` Badari Pulavarty
2008-01-29 5:18 ` Yasunori Goto
2008-01-30 0:31 ` Badari Pulavarty
2008-01-30 1:13 ` Yasunori Goto [this message]
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=20080130095002.4CCC.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).