Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934267AbZGQJBz (ORCPT ); Fri, 17 Jul 2009 05:01:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S934226AbZGQJBy (ORCPT ); Fri, 17 Jul 2009 05:01:54 -0400 Received: from smtp-out.google.com ([216.239.33.17]:62619 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934241AbZGQJBx (ORCPT ); Fri, 17 Jul 2009 05:01:53 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id: references:user-agent:mime-version:content-type:x-system-of-record; b=hiCWFgXPcclwgw28YSU98Zymve21qgI39HWnYLSDDsOoaPH8Xl1qCsMBDHwbpaYbL Ludy1mru1TW2i2v5dP6LQ== Date: Fri, 17 Jul 2009 02:01:41 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: KOSAKI Motohiro cc: Lee Schermerhorn , Miao Xie , Ingo Molnar , Peter Zijlstra , Christoph Lameter , Paul Menage , Nick Piggin , Yasunori Goto , Pekka Enberg , linux-mm , LKML , Andrew Morton Subject: Re: [BUG] set_mempolicy(MPOL_INTERLEAV) cause kernel panic In-Reply-To: <20090717090003.A903.A69D9226@jp.fujitsu.com> Message-ID: References: <1247679064.4089.26.camel@useless.americas.hpqcorp.net> <20090717090003.A903.A69D9226@jp.fujitsu.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 666 Lines: 19 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/