linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel ML <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] Register sysfs file for hotpluged new node take 2.
Date: Sat, 20 May 2006 21:18:54 +0900	[thread overview]
Message-ID: <20060520104215.BBB9.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <1148058107.6623.160.camel@localhost.localdomain>

> On Thu, 2006-05-18 at 14:50 +0900, Yasunori Goto wrote:
> > +       if (new_pgdat) {
> > +               ret = register_one_node(nid);
> > +               /*
> > +                * If sysfs file of new node can't create, cpu on the node
> > +                * can't be hot-added. There is no rollback way now.
> > +                * So, check by BUG_ON() to catch it reluctantly..
> > +                */
> > +               BUG_ON(ret);
> > +       } 
> 
> How about we register the node in sysfs _before_ it is
> set_node_online()'d?  Effectively an empty node with no memory and no
> CPUs.  It might be a wee bit confusing to any user tools watching the
> NUMA sysfs stuff, but I think it beats a BUG().

Hmmm. I'm not sure what will happen when sysfs file is accessed by user
at this time.  I think this issue should be going to be solved when
__remove_memory() and pgdat offline will be created.

Thanks for your comment.

-- 
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>

      reply	other threads:[~2006-05-20 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18  5:50 Yasunori Goto
2006-05-19 10:18 ` Yasunori Goto
2006-05-19 17:01 ` Dave Hansen
2006-05-20 12:18   ` 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=20060520104215.BBB9.Y-GOTO@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=akpm@osdl.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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