public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-ia64@vger.kernel.org, tony.luck@intel.com,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] remove empty node at boot time
Date: Mon, 10 Jul 2006 17:03:03 +0000	[thread overview]
Message-ID: <200607101103.03849.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20060710141903.424ba3db.kamezawa.hiroyu@jp.fujitsu.com>

On Sunday 09 July 2006 23:19, KAMEZAWA Hiroyuki wrote:
> Could you try this patch ? (against 2.6.18-rc1)

Your patch does fix it.  But I'm worried about removing
empty nodes at boot-time.  I want to support the following
scenario:

  node 0: 1 enabled CPU, 3 disabled CPUs, no local memory
  node 1: 4 disabled CPUs, no local memory
  node 2: no CPUs, big interleaved memory across nodes 0 & 1

At run-time, I'd like to be able to enable any or all of the
7 disabled CPUs.  If you remove the "empty" node 1 at boot-time,
it sounds like I won't be able to enable its CPUs later.

Bjorn

  reply	other threads:[~2006-07-10 17:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 11:04 [PATCH] remove empty node at boot time KAMEZAWA Hiroyuki
2006-07-07 23:26 ` Bjorn Helgaas
2006-07-10  0:34   ` KAMEZAWA Hiroyuki
2006-07-10  2:38     ` Bjorn Helgaas
2006-07-10  3:29       ` KAMEZAWA Hiroyuki
2006-07-10  5:19       ` KAMEZAWA Hiroyuki
2006-07-10 17:03         ` Bjorn Helgaas [this message]
2006-07-11  6:55           ` KAMEZAWA Hiroyuki
2006-07-11 15:37             ` Bjorn Helgaas

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=200607101103.03849.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=akpm@osdl.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@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