From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme pci: fix nvme_setup_irqs()
Date: Mon, 7 Jan 2019 09:24:06 -0700 [thread overview]
Message-ID: <20190107162406.GB12916@localhost.localdomain> (raw)
In-Reply-To: <20190103013439.26700-1-ming.lei@redhat.com>
On Thu, Jan 03, 2019@09:34:39AM +0800, Ming Lei wrote:
> When -ENOSPC is returned from pci_alloc_irq_vectors_affinity(),
> we still try to allocate multiple irq vectors again, so irq queues
> covers the admin queue actually. But we don't consider that, then
> number of the allocated irq vector may be same with sum of
> io_queues[HCTX_TYPE_DEFAULT] and io_queues[HCTX_TYPE_READ], this way
> is obviously wrong, and finally breaks nvme_pci_map_queues(), and
> warning from pci_irq_get_affinity() is triggered.
>
> IRQ queues should cover admin queues, this patch makes this
> point explicitely in nvme_calc_io_queues().
>
> We got severl boot failure internal report on aarch64, so please
> consider to fix it in v4.20.
I see what you saying with the inconsistent meaning for irq_queues, though
4.20 should be fine.
I hope we can make the irq sets easier to use in the future, but your
patch looks correct for the current interface.
Reviewed-by: Keith Busch <keith.busch at intel.com>
> Fixes: 6451fe73fa0f ("nvme: fix irq vs io_queue calculations")
> Cc: Keith Busch <keith.busch at intel.com>
> Cc: Jens Axboe <axboe at fb.com>
> Signed-off-by: Ming Lei <ming.lei at redhat.com>
next prev parent reply other threads:[~2019-01-07 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 1:34 [PATCH] nvme pci: fix nvme_setup_irqs() Ming Lei
2019-01-07 1:31 ` Ming Lei
2019-01-07 16:24 ` Keith Busch [this message]
2019-01-10 0:51 ` Ming Lei
2019-01-15 5:51 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190107162406.GB12916@localhost.localdomain \
--to=keith.busch@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.