On Tue, 2008-03-04 at 01:35 -0600, Paul Jackson wrote:Yeah, that would definitely be awkward.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.