[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0907170158050.13151@chino.kir.corp.google.com>
Date: Fri, 17 Jul 2009 02:01:41 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
cc: Lee Schermerhorn <Lee.Schermerhorn@...com>,
Miao Xie <miaox@...fujitsu.com>, Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Christoph Lameter <cl@...ux-foundation.org>,
Paul Menage <menage@...gle.com>,
Nick Piggin <nickpiggin@...oo.com.au>,
Yasunori Goto <y-goto@...fujitsu.com>,
Pekka Enberg <penberg@...helsinki.fi>,
linux-mm <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [BUG] set_mempolicy(MPOL_INTERLEAV) cause kernel panic
On Fri, 17 Jul 2009, KOSAKI Motohiro wrote:
> This patch seems band-aid patch. it will change memory-hotplug behavior.
> Please imazine following scenario:
>
> 1. numactl interleave=all process-A
> 2. memory hot-add
>
> before 2.6.30:
> -> process-A can use hot-added memory
>
That apparently depends on the architecture since Lee said top_cpuset
reflects node_possible_map on ia64 and node_online_map on x86_64.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists