From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754877AbZBSFpx (ORCPT ); Thu, 19 Feb 2009 00:45:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751265AbZBSFpo (ORCPT ); Thu, 19 Feb 2009 00:45:44 -0500 Received: from rcsinet11.oracle.com ([148.87.113.123]:18011 "EHLO rgminet11.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751432AbZBSFpo (ORCPT ); Thu, 19 Feb 2009 00:45:44 -0500 Message-ID: <499CF229.9040904@oracle.com> Date: Wed, 18 Feb 2009 21:46:17 -0800 From: Randy Dunlap Organization: Oracle Linux Engineering User-Agent: Thunderbird 2.0.0.6 (X11/20070801) MIME-Version: 1.0 To: Li Zefan CC: Andrew Morton , Paul Menage , LKML Subject: Re: [PATCH] cpuset: various documentation fixes and updates References: <499CBFDF.1070503@cn.fujitsu.com> <499CED75.9030907@oracle.com> <499CF10C.1010104@cn.fujitsu.com> In-Reply-To: <499CF10C.1010104@cn.fujitsu.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Source-IP: acsmt701.oracle.com [141.146.40.71] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A010202.499CF1F6.0049:SCFSTAT928724,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Li Zefan wrote: >>> If a cpuset has its 'cpus' modified, then each task in that cpuset >>> will have its allowed CPU placement changed immediately. Similarly, >>> -if a tasks pid is written to a cpusets 'tasks' file, in either its >>> -current cpuset or another cpuset, then its allowed CPU placement is >>> -changed immediately. If such a task had been bound to some subset >>> -of its cpuset using the sched_setaffinity() call, the task will be >>> -allowed to run on any CPU allowed in its new cpuset, negating the >>> -affect of the prior sched_setaffinity() call. >>> +if a tasks pid is written to another cpusets 'tasks' file, then its >> task's pid cpuset's >> > > Paul Jackson is the original author of this document, and he once said he > doesn't like to use foo's but is used to use foos, so I think I'm not > going to correct them all through this doc, at least not in this patch. :) I'll fix them then, unless Paul Menage et al disagree. -- ~Randy