From: Andi Kleen <andi@firstfloor.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
kosaki.motohiro@gmail.com, mingo@kernel.org, hpa@zytor.com,
srivatsa.bhat@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-mm@kvack.org
Subject: Re: [Bug fix PATCH v2] numa, cpu hotplug: Change links of CPU and node when changing node number by onlining CPU
Date: Tue, 23 Apr 2013 09:06:55 -0700 [thread overview]
Message-ID: <m2y5c9ut7k.fsf@firstfloor.org> (raw)
In-Reply-To: <20130422153541.04ba682f13910cfede0d2ff7@linux-foundation.org> (Andrew Morton's message of "Mon, 22 Apr 2013 15:35:41 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
>
> Would it not be better to fix this by assigning those CPUs to their real,
> memoryless node right at the initial boot? Or is there something in
> the kernel which makes cpus-on-a-memoryless-node not work correctly?
I probably added this originally. The original reason was that long
ago the VM was broken with memory less nodes. These days it is likely
obsolete.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
<kosaki.motohiro@gmail.com>, <mingo@kernel.org>, <hpa@zytor.com>,
<srivatsa.bhat@linux.vnet.ibm.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<linux-mm@kvack.org>
Subject: Re: [Bug fix PATCH v2] numa, cpu hotplug: Change links of CPU and node when changing node number by onlining CPU
Date: Tue, 23 Apr 2013 09:06:55 -0700 [thread overview]
Message-ID: <m2y5c9ut7k.fsf@firstfloor.org> (raw)
In-Reply-To: <20130422153541.04ba682f13910cfede0d2ff7@linux-foundation.org> (Andrew Morton's message of "Mon, 22 Apr 2013 15:35:41 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
>
> Would it not be better to fix this by assigning those CPUs to their real,
> memoryless node right at the initial boot? Or is there something in
> the kernel which makes cpus-on-a-memoryless-node not work correctly?
I probably added this originally. The original reason was that long
ago the VM was broken with memory less nodes. These days it is likely
obsolete.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-04-23 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 5:23 [Bug fix PATCH v2] numa, cpu hotplug: Change links of CPU and node when changing node number by onlining CPU Yasuaki Ishimatsu
2013-04-19 5:23 ` Yasuaki Ishimatsu
2013-04-22 22:35 ` Andrew Morton
2013-04-22 22:35 ` Andrew Morton
2013-04-23 0:04 ` Yasuaki Ishimatsu
2013-04-23 0:04 ` Yasuaki Ishimatsu
2013-04-23 0:34 ` Andrew Morton
2013-04-23 0:34 ` Andrew Morton
2013-04-23 1:24 ` Yasuaki Ishimatsu
2013-04-23 1:24 ` Yasuaki Ishimatsu
2013-04-23 16:06 ` Andi Kleen [this message]
2013-04-23 16:06 ` Andi Kleen
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=m2y5c9ut7k.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.