From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Brent Casavant <bcasavan@sgi.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-ia64@vger.kernel.org, ak@suse.de,
Yasunori Goto <ygoto@us.fujitsu.com>
Subject: Re: [PATCH 0/3] NUMA boot hash allocation interleaving
Date: Wed, 15 Dec 2004 00:28:04 +0000 [thread overview]
Message-ID: <41BF8514.1030208@jp.fujitsu.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F028C1639@scsmsx401.amr.corp.intel.com>
Luck, Tony wrote:
>>this behavior is turned on by default only for IA64 NUMA systems
>
>
>>A boot line parameter "hashdist" can be set to override the default
>>behavior.
>
>
>
> Note to node hot-plug developers ... if this patch goes in you
> will also want to disable this behaviour, otherwaise all nodes
> become non-removeable (unless you can transparently re-locate the
> physical memory backing all these tables).
(adding CC to LHMS)
I think GFP_HOTREMOVABLE , which Goto is proposing, will work well
when we want MEMORY_HOTPLUG.
Thnaks.
--Kame <kamezawa.hiroyu@jp.fujitsu.com>
>
> -Tony
WARNING: multiple messages have this Message-ID (diff)
From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Brent Casavant <bcasavan@sgi.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-ia64@vger.kernel.org, ak@suse.de,
Yasunori Goto <ygoto@us.fujitsu.com>
Subject: Re: [PATCH 0/3] NUMA boot hash allocation interleaving
Date: Wed, 15 Dec 2004 09:28:04 +0900 [thread overview]
Message-ID: <41BF8514.1030208@jp.fujitsu.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F028C1639@scsmsx401.amr.corp.intel.com>
Luck, Tony wrote:
>>this behavior is turned on by default only for IA64 NUMA systems
>
>
>>A boot line parameter "hashdist" can be set to override the default
>>behavior.
>
>
>
> Note to node hot-plug developers ... if this patch goes in you
> will also want to disable this behaviour, otherwaise all nodes
> become non-removeable (unless you can transparently re-locate the
> physical memory backing all these tables).
(adding CC to LHMS)
I think GFP_HOTREMOVABLE , which Goto is proposing, will work well
when we want MEMORY_HOTPLUG.
Thnaks.
--Kame <kamezawa.hiroyu@jp.fujitsu.com>
>
> -Tony
WARNING: multiple messages have this Message-ID (diff)
From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Brent Casavant <bcasavan@sgi.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-ia64@vger.kernel.org, ak@suse.de,
Yasunori Goto <ygoto@us.fujitsu.com>
Subject: Re: [PATCH 0/3] NUMA boot hash allocation interleaving
Date: Wed, 15 Dec 2004 09:28:04 +0900 [thread overview]
Message-ID: <41BF8514.1030208@jp.fujitsu.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F028C1639@scsmsx401.amr.corp.intel.com>
Luck, Tony wrote:
>>this behavior is turned on by default only for IA64 NUMA systems
>
>
>>A boot line parameter "hashdist" can be set to override the default
>>behavior.
>
>
>
> Note to node hot-plug developers ... if this patch goes in you
> will also want to disable this behaviour, otherwaise all nodes
> become non-removeable (unless you can transparently re-locate the
> physical memory backing all these tables).
(adding CC to LHMS)
I think GFP_HOTREMOVABLE , which Goto is proposing, will work well
when we want MEMORY_HOTPLUG.
Thnaks.
--Kame <kamezawa.hiroyu@jp.fujitsu.com>
>
> -Tony
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-12-15 0:28 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 17:53 [PATCH 0/3] NUMA boot hash allocation interleaving Brent Casavant
2004-12-14 17:53 ` Brent Casavant
2004-12-14 17:53 ` Brent Casavant
2004-12-14 18:32 ` Luck, Tony
2004-12-14 18:32 ` Luck, Tony
2004-12-14 18:32 ` Luck, Tony
2004-12-15 0:28 ` Hiroyuki KAMEZAWA [this message]
2004-12-15 0:28 ` Hiroyuki KAMEZAWA
2004-12-15 0:28 ` Hiroyuki KAMEZAWA
2004-12-14 18:59 ` Martin J. Bligh
2004-12-14 18:59 ` Martin J. Bligh
2004-12-14 18:59 ` Martin J. Bligh
2004-12-14 19:13 ` Andi Kleen
2004-12-14 19:13 ` Andi Kleen
2004-12-14 19:13 ` Andi Kleen
2004-12-14 19:48 ` Brent Casavant
2004-12-14 19:48 ` Brent Casavant
2004-12-14 19:48 ` Brent Casavant
2004-12-14 20:08 ` Martin J. Bligh
2004-12-14 20:08 ` Martin J. Bligh
2004-12-14 20:08 ` Martin J. Bligh
2004-12-14 23:24 ` Brent Casavant
2004-12-14 23:24 ` Brent Casavant
2004-12-14 23:24 ` Brent Casavant
2004-12-14 22:00 ` Martin J. Bligh
2004-12-14 22:00 ` Martin J. Bligh
2004-12-14 22:00 ` Martin J. Bligh
2004-12-15 4:58 ` Andi Kleen
2004-12-15 4:58 ` Andi Kleen
2004-12-15 4:58 ` Andi Kleen
2004-12-15 14:47 ` Anton Blanchard
2004-12-15 14:47 ` Anton Blanchard
2004-12-15 14:47 ` Anton Blanchard
2004-12-15 23:37 ` Brent Casavant
2004-12-15 23:37 ` Brent Casavant
2004-12-15 23:37 ` Brent Casavant
2004-12-16 5:02 ` Andi Kleen
2004-12-16 5:02 ` Andi Kleen
2004-12-16 5:02 ` Andi Kleen
2004-12-16 5:13 ` Anton Blanchard
2004-12-16 14:18 ` Jose R. Santos
2004-12-16 14:18 ` Jose R. Santos
2004-12-16 14:18 ` Jose R. Santos
2004-12-20 16:56 ` Jose R. Santos
2004-12-20 16:56 ` Jose R. Santos
2004-12-20 16:56 ` Jose R. Santos
2004-12-21 11:46 ` Anton Blanchard
2004-12-21 11:46 ` Anton Blanchard
2004-12-21 11:46 ` Anton Blanchard
2004-12-21 16:23 ` Brent Casavant
2004-12-21 16:23 ` Brent Casavant
2004-12-21 16:23 ` Brent Casavant
2004-12-23 2:19 ` Jose R. Santos
2004-12-23 2:19 ` Jose R. Santos
2004-12-23 2:19 ` Jose R. Santos
2004-12-15 4:08 ` Andi Kleen
2004-12-15 4:08 ` Andi Kleen
2004-12-15 4:08 ` Andi Kleen
2004-12-15 7:14 ` Martin J. Bligh
2004-12-15 7:14 ` Martin J. Bligh
2004-12-15 7:14 ` Martin J. Bligh
2004-12-15 7:17 ` Andi Kleen
2004-12-15 7:17 ` Andi Kleen
2004-12-15 7:17 ` Andi Kleen
2004-12-15 15:08 ` Martin J. Bligh
2004-12-15 15:08 ` Martin J. Bligh
2004-12-15 15:08 ` Martin J. Bligh
2004-12-15 18:24 ` Brent Casavant
2004-12-15 18:24 ` Brent Casavant
2004-12-15 18:24 ` Brent Casavant
2004-12-15 7:41 ` Eric Dumazet
2004-12-15 7:41 ` Eric Dumazet
2004-12-15 7:41 ` Eric Dumazet
2004-12-15 7:46 ` Andi Kleen
2004-12-15 7:46 ` Andi Kleen
2004-12-15 7:46 ` Andi Kleen
2004-12-15 9:14 ` Andi Kleen
2004-12-15 9:14 ` Andi Kleen
2004-12-15 9:14 ` Andi Kleen
2004-12-14 23:24 ` Nick Piggin
2004-12-14 23:24 ` Nick Piggin
2004-12-14 23:24 ` Nick Piggin
2004-12-14 19:30 ` Brent Casavant
2004-12-14 19:30 ` Brent Casavant
2004-12-14 19:30 ` Brent Casavant
2004-12-14 20:10 ` Martin J. Bligh
2004-12-14 20:10 ` Martin J. Bligh
2004-12-14 20:10 ` Martin J. Bligh
2004-12-15 17:25 ` Luck, Tony
2004-12-15 17:25 ` Luck, Tony
2004-12-15 17:25 ` Luck, Tony
-- strict thread matches above, loose matches on Subject: below --
2004-12-20 23:36 Brent Casavant
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=41BF8514.1030208@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=ak@suse.de \
--cc=bcasavan@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tony.luck@intel.com \
--cc=ygoto@us.fujitsu.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 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.