Re: [PATCH 00/16] dyn_array and nr_irqs support v2

[Eric W. Biederman]

"H. Peter Anvin" <hpa@xxxxxxxxx> writes:

> Eric W. Biederman wrote:
>>
>> Having a human readable name like: eth0irq22 or hbairq5 is likely just
>> as good in the case of msi.  Still all of the users interfaces today take
> numbers.
>> So we are stuck with dealing with numbers for a long time to come.
>>
>
> Long sparse numbers are messy, too, though.  It might be interesting to have a
> routine somewhere like "irq_name()" to output a human-readable IRQ name, which
> in case of MSI-X could contain the PCI device name.

Yes.  I want the option of using those bits.  It might not be smart to
use them to encode a physical location and the irq number but just
having the option would be nice.

Making /proc/interrupts useful without breaking user space is going to be
an interesting challenge one of these days.

Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/