[PATCH RFC 00/77] Re-design MSI/MSI-X interrupts enablement pattern
David Laight
David.Laight at ACULAB.COM
Fri Oct 4 04:31:49 EDT 2013
> > It seems to me that a more useful interface would take a minimum and
> > maximum number of vectors from the driver. This wouldn't allow the
> > driver to specify that it could only accept, say, any even number within
> > a certain range, but you could still leave the current functions
> > available for any driver that needs that.
>
> Mmmm.. I am not sure I am getting it. Could you please rephrase?
One possibility is for drivers than can use a lot of interrupts to
request a minimum number initially and then request the additional
ones much later on.
That would make it less likely that none will be available for
devices/drivers that need them but are initialised later.
David
More information about the Linux-nvme
mailing list