From: Shaohui Zheng <shaohui.zheng@intel.com>
To: David Rientjes <rientjes@google.com>
Cc: Eric B Munson <emunson@mgebm.net>,
Shaohui Zheng <shaohui.zheng@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
haicheng.li@linux.intel.com, lethal@linux-sh.org,
Andi Kleen <ak@linux.intel.com>,
dave@linux.vnet.ibm.com, Greg Kroah-Hartman <gregkh@suse.de>,
Haicheng Li <haicheng.li@intel.com>
Subject: Re: [1/7,v8] NUMA Hotplug Emulator: documentation
Date: Thu, 9 Dec 2010 08:23:02 +0800 [thread overview]
Message-ID: <20101209002302.GB5798@shaohui> (raw)
In-Reply-To: <alpine.DEB.2.00.1012081315040.15658@chino.kir.corp.google.com>
On Wed, Dec 08, 2010 at 01:16:10PM -0800, David Rientjes wrote:
> On Wed, 8 Dec 2010, Eric B Munson wrote:
>
> > Shaohui,
> >
> > I was able to online a cpu to node 0 successfully. My problem was that I did
> > not take the cpu offline before I released it. Everything looks to be working
> > for me.
> >
>
> I think it should fail more gracefully than triggering WARN_ON()s because
> of duplicate sysfs dentries though, right?
Yes, we should do more checking on the return value, the duplicate dentries can
be avoided.
Another solution: force user to offline the cpu before we do cpu release.
--
Thanks & Regards,
Shaohui
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-12-09 1:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 1:00 [0/7,v8] NUMA Hotplug Emulator (v8) shaohui.zheng
2010-12-07 1:00 ` [1/7,v8] NUMA Hotplug Emulator: documentation shaohui.zheng
2010-12-07 18:24 ` Eric B Munson
2010-12-07 23:20 ` Shaohui Zheng
2010-12-08 17:46 ` Eric B Munson
2010-12-09 0:09 ` Shaohui Zheng
2010-12-08 18:16 ` Eric B Munson
2010-12-08 21:16 ` David Rientjes
2010-12-09 0:23 ` Shaohui Zheng [this message]
2010-12-08 21:18 ` David Rientjes
2010-12-09 0:33 ` Shaohui Zheng
2010-12-07 1:00 ` [2/7,v8] NUMA Hotplug Emulator: Add numa=possible option shaohui.zheng
2010-12-07 1:00 ` [3/7,v8] NUMA Hotplug Emulator: Add node hotplug emulation shaohui.zheng
2010-12-07 1:00 ` [4/7,v8] NUMA Hotplug Emulator: Abstract cpu register functions shaohui.zheng
2010-12-07 1:00 ` [5/7,v8] NUMA Hotplug Emulator: Support cpu probe/release in x86_64 shaohui.zheng
2010-12-08 21:36 ` David Rientjes
2010-12-09 9:37 ` Tejun Heo
2010-12-10 8:01 ` Zheng, Shaohui
2010-12-10 1:35 ` Zheng, Shaohui
2010-12-07 1:00 ` [6/7,v8] NUMA Hotplug Emulator: Fake CPU socket with logical CPU on x86 shaohui.zheng
2010-12-07 1:00 ` [7/7,v8] NUMA Hotplug Emulator: Implement per-node add_memory debugfs interface shaohui.zheng
2010-12-08 21:31 ` David Rientjes
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=20101209002302.GB5798@shaohui \
--to=shaohui.zheng@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=emunson@mgebm.net \
--cc=gregkh@suse.de \
--cc=haicheng.li@intel.com \
--cc=haicheng.li@linux.intel.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=shaohui.zheng@linux.intel.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).