Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759304AbYFDJbM (ORCPT ); Wed, 4 Jun 2008 05:31:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752649AbYFDJa7 (ORCPT ); Wed, 4 Jun 2008 05:30:59 -0400 Received: from smtp-out.google.com ([216.239.33.17]:25525 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752211AbYFDJa6 (ORCPT ); Wed, 4 Jun 2008 05:30:58 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:message-id:date:from:to:subject:cc:in-reply-to: mime-version:content-type:content-transfer-encoding: content-disposition:references; b=UJ+ZQYXJu2e7hfxtPUObG0Mo6nJlQCIw3cceVRiE4N9K7V686sIPbnugZqEvTYgvN Zk3ZbnA9nkoaLfUhoT9/Q== Message-ID: <6599ad830806040230l24bd1201y3cc0ea0273d835ad@mail.gmail.com> Date: Wed, 4 Jun 2008 02:30:51 -0700 From: "Paul Menage" To: miaox@cn.fujitsu.com Subject: Re: [PATCH 2/2] cpusets: update tasks' cpus_allowed and mems_allowed after CPU/NODE offline/online Cc: "Andrew Morton" , Linux-Kernel , "Paul Jackson" In-Reply-To: <4845F864.8060102@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4845F864.8060102@cn.fujitsu.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 699 Lines: 17 On Tue, Jun 3, 2008 at 7:05 PM, Miao Xie wrote: > > Maybe we need to add a flag in the task_struct to mark which task can't be > unbound? Yes, something like a PF_CPU_BOUND flag that gets set in kthread_bind() and checked for in set_cpus_allowed() would be the right way to handle that. We have an internal change like that against an older kernel verison - I'll see if I can find someone to forward port it and send it in. Paul -- 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/