On Wed, Feb 28, 2018 at 05:47:26PM +0100, Christoph Hellwig wrote: > Note that we originally allocates irqs this way, and Keith changed > it a while ago for good reasons. So I'd really like to see good > reasons for moving away from this, and some heuristics to figure > out which way to use. E.g. if the device supports more irqs than > I/O queues your scheme might always be fine.
If all CPUs for the 1st IRQ vector of admin queue are offline, then I guess NVMe can't work any more. So looks it is a good idea to make admin queue's IRQ vector assigned as non-managed IRQs. Thanks, Ming
