Date: Thu, 21 Jun 2007 14:16:35 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Cc: pj@sgi.com, clameter@sgi.com, linux-kernel@vger.kernel.org,
       Dinakar Guniguntala <dino@in.ibm.com>, akpm@linux-foundation.org
Subject: Re: cpuset attach_task to touch per-cpu kernel threads?
Message-ID: <20070621121635.GB19811@elte.hu>
References: <20070621014935.GF10980@linux.vnet.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070621014935.GF10980@linux.vnet.ibm.com>
User-Agent: Mutt/1.5.14 (2007-02-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 717
Lines: 17


* Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> wrote:

> But I am wondering if attach_task() should leave kernel threads alone 
> and act only upon user-space threads. Or maybe allow movement if it 
> doesn't result in changing kernel-threads's cpu affinity.

yeah, i'd agree with the latter. We could also special-case the 
migration thread to never be migrated itself. (although that's not the 
end of the matter either - two ksoftirqds on a cpu are not healty)

	Ingo
-
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/