Jens Axboe 30e066286e nvme: fix boot hang with only being able to get one IRQ vector
NVMe always asks for io_queues + 1 worth of IRQ vectors, which
means that even when we scale all the way down, we still ask
for 2 vectors and get -ENOSPC in return if the system can't
support more than 1.

Getting just 1 vector is fine, it just means that we'll have
1 IO queue and 1 admin queue, with a shared vector between them.
Check for this case and don't add our + 1 if it happens.

Fixes: 3b6592f70ad7 ("nvme: utilize two queue maps, one for reads and one for writes")
Reported-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2018-11-14 10:13:50 -07:00
..
2018-11-02 11:22:45 -07:00
2018-11-01 18:34:46 -07:00
2018-10-29 15:16:01 -07:00
2018-10-27 09:24:24 -07:00
2018-10-25 06:50:48 -07:00
2018-10-16 11:13:50 +02:00
2018-10-25 06:50:48 -07:00
2018-10-29 10:38:10 -07:00
2018-10-31 08:54:16 -07:00
2018-11-02 11:25:48 -07:00
2018-10-31 10:53:29 -07:00
2018-10-31 16:47:55 -07:00
2018-10-25 06:31:56 -07:00
2018-11-01 14:45:38 -07:00
2018-10-26 14:36:21 -07:00
2018-10-22 17:30:06 +01:00
2018-10-26 08:14:13 -07:00
2018-11-01 08:42:21 -07:00
2018-10-26 12:09:58 -07:00
2018-10-29 15:16:01 -07:00
2018-11-07 13:42:32 -07:00
2018-10-31 08:54:16 -07:00
2018-10-25 06:19:15 -07:00
2018-10-31 10:53:29 -07:00
2018-11-07 13:42:32 -07:00
2018-10-31 08:54:16 -07:00
2018-10-31 11:01:38 -07:00
2018-11-01 14:42:49 -07:00
2018-10-31 11:41:37 -07:00