Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758082Ab0BXVIU (ORCPT ); Wed, 24 Feb 2010 16:08:20 -0500 Received: from smtp-out.google.com ([216.239.33.17]:30878 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757767Ab0BXVIS (ORCPT ); Wed, 24 Feb 2010 16:08:18 -0500 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=ER5gbGhjNPmM3p7fHJmABlDasGhA4QrzN+263JHTsyFdHbzZdI45V6yjgKGti1R/G J2XvoZj4DDbaFoq25rdNA== Date: Wed, 24 Feb 2010 13:08:12 -0800 (PST) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Miao Xie cc: Nick Piggin , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Lee Schermerhorn Subject: Re: [regression] cpuset,mm: update tasks' mems_allowed in time (58568d2) In-Reply-To: <4B84F2FD.6030605@cn.fujitsu.com> Message-ID: References: <20100218134921.GF9738@laptop> <20100219033126.GI9738@laptop> <4B827043.3060305@cn.fujitsu.com> <4B838490.1050908@cn.fujitsu.com> <4B839E9D.8020604@cn.fujitsu.com> <4B84F2FD.6030605@cn.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: 783 Lines: 16 On Wed, 24 Feb 2010, Miao Xie wrote: > I think it is not a big deal because it is safe and doesn't cause any problem. > Beside that, task->cpus_allowed is initialized to cpu_possible_mask on the no-cpuset > kernel, so using cpu_possible_mask to initialize task->cpus_allowed is reasonable. > (top cpuset is a special cpuset, isn't it?) > I'm suprised that I can create a descendant cpuset of top_cpuset that cannot include all of its parents' cpus and that the root cpuset's cpus mask doesn't change when cpus are onlined/offlined. -- 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/