linux-kernel - Re: cpuset attach_task to touch per-cpu kernel threads?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070621121635.GB19811@elte.hu>
Date:	Thu, 21 Jun 2007 14:16:35 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>
Cc:	pj@....com, clameter@....com, linux-kernel@...r.kernel.org,
	Dinakar Guniguntala <dino@...ibm.com>,
	akpm@...ux-foundation.org
Subject: Re: cpuset attach_task to touch per-cpu kernel threads?


* Srivatsa Vaddagiri <vatsa@...ux.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/