* Eric W. Biederman <[email protected]> wrote:
> In addition the cases I can think of allowed_affinity is the wrong
> name. suggested_affinity sounds like what you are trying to implement
> and when it is merely a suggestion and not a hard limit it doesn't
> make sense to export like this.
well, there are interrupts that must be tied to a single CPU and must
never be moved away. For example per-CPU clock-events-source interrupts
are such. So allowed_affinity very much exists.
also there might be hardware that can only route a given IRQ to a subset
of CPUs. While setting set_affinity allows the irqbalance-daemon to
'probe' this mask, it's a far from optimal API.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
