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-mm <linux-mm@kvack.org>,
	Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Register sysfs file for hotpluged new node
Date: Wed, 17 May 2006 14:48:41 +0900	[thread overview]
Message-ID: <20060517111236.21AC.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <1147791091.6623.93.camel@localhost.localdomain>

> On Tue, 2006-05-16 at 21:23 +0900, Yasunori Goto wrote:
> > +       /*
> > +        * register this node to sysfs.
> > +        * this is depends on topology. So each arch has its own.
> > +        */
> > +       if (new_pgdat){
> > +               ret = arch_register_node(nid);
> > +               BUG_ON(ret);
> > +       } 
> 
> Please don't do BUG_ON()s for things like this.  Memory hotplug _should_
> handle failures from top to bottom and not screw you over.  It isn't a
> crime or a bug to be out of memory.  

Basically, I would like to agree. 
But, there is no way to roll back from here now.
If online_node_map is set once, then new pgdat might be touched.
There is no way to disable them.

And I suppose it is not good thing that creating sysfs file of new node
before setting online_node_map. It means user interface is shown
before system initialization completion.

(In addition, remove_memory() is not yet....)

If return code of arch_register_node is ignored, 
cpu hotplug will work without new node's file.
When we tried cpu hotplug on it, it was cause of stack dump at last.

> Have you run this past the ppc maintainers?

Nope. I just tried cross compile.
I want powerpc box for test....


Thanks.

-- 
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-17  5:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 12:23 Yasunori Goto
2006-05-16 14:51 ` Dave Hansen
2006-05-17  5:48   ` Yasunori Goto [this message]
2006-05-16 14:55 ` Dave Hansen
2006-05-17  3:22   ` Yasunori Goto

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=20060517111236.21AC.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