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: 3b6592f70a ("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
..
host	nvme: fix boot hang with only being able to get one IRQ vector	2018-11-14 10:13:50 -07:00
target	Merge branch 'work.afs' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs	2018-11-01 19:58:52 -07:00
Kconfig	nvme: use menu Kconfig interface	2017-10-04 09:43:57 +02:00
Makefile	nvmet: add a generic NVMe target	2016-07-05 11:30:33 -06:00