linux-kernel - Re: [RFC/PATCH] cpuset: cpuset irq affinities

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]

Date:	Tue, 04 Mar 2008 11:52:37 -0800
From:	Max Krasnyanskiy <maxk@...lcomm.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC:	Paul Jackson <pj@....com>, mingo@...e.hu, tglx@...utronix.de,
	oleg@...sign.ru, rostedt@...dmis.org, linux-kernel@...r.kernel.org,
	rientjes@...gle.com
Subject: Re: [RFC/PATCH] cpuset: cpuset irq affinities

Peter Zijlstra wrote:
> On Tue, 2008-03-04 at 01:35 -0600, Paul Jackson wrote:
>> Peter wrote:
>>> OK, understood, I'll try and come up with yet another scheme :-)
>> Would your per-cpuset 'irqs' file work if, unlike pids in the 'tasks' file,
>> we allowed the same irq to be listed in multiple 'irqs' files?
> 
> I did think of that, but that seems rather awkward. For one, how would
> you remove an irq from a cpuset?
> 
> Secondly, the beauty of the current solution is that we use
> irq_desc->cs->cpus_allowed, if it were in multiple sets, we'd have to
> iterate a list, and cpus_or() the bunch.
> 
Yeah, that would definitely be awkward.

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