From: Ming Lei <ming.lei@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Keith Busch <keith.busch@intel.com>,
linux-pci@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] PCI/MSI: preference to returning -ENOSPC from pci_alloc_irq_vectors_affinity
Date: Wed, 16 Jan 2019 06:46:32 +0800 [thread overview]
Message-ID: <20190115224631.GA22558@ming.t460p> (raw)
In-Reply-To: <20190115193135.GH33971@google.com>
Hi Bjorn,
I think Christoph and Jens are correct, we should make this patch into
5.0 because the issue is triggered since 3b6592f70ad7b4c2 ("nvme: utilize
two queue maps, one for reads and one for writes"), which is merged to
5.0-rc.
For example, before 3b6592f70ad7b4c2, one nvme controller may be
allocated 64 irq vectors; but after that commit, only 1 irq vector
is assigned to this controller.
On Tue, Jan 15, 2019 at 01:31:35PM -0600, Bjorn Helgaas wrote:
> On Tue, Jan 15, 2019 at 09:22:45AM -0700, Jens Axboe wrote:
> > On 1/15/19 6:11 AM, Christoph Hellwig wrote:
> > > On Mon, Jan 14, 2019 at 05:23:39PM -0600, Bjorn Helgaas wrote:
> > >> Applied to pci/msi for v5.1, thanks!
> > >>
> > >> If this is something that should be in v5.0, let me know and include the
> > >> justification, e.g., something we already merged for v5.0 or regression
> > >> info, etc, and a Fixes: line, and I'll move it to for-linus.
> > >
> > > I'd be tempted to queues this up for 5.0. Ming, what is your position?
> >
> > I think we should - the API was introduced in this series, I think there's
> > little (to no) reason NOT to fix it for 5.0.
>
> I'm guessing the justification goes something like this (I haven't
> done all the research, so I'll leave it to Ming to fill in the details):
>
> pci_alloc_irq_vectors_affinity() was added in v4.x by XXXX ("...").
dca51e7892fa3b ("nvme: switch to use pci_alloc_irq_vectors")
> It had this return value defect then, but its min_vecs/max_vecs
> parameters removed the need for callers to interatively reduce the
> number of IRQs requested and retry the allocation, so they didn't
> need to distinguish -ENOSPC from -EINVAL.
>
> In v5.0, XXX ("...") added IRQ sets to the interface, which
3b6592f70ad7b4c2 ("nvme: utilize two queue maps, one for reads and one for writes")
> reintroduced the need to check for -ENOSPC and possibly reduce the
> number of IRQs requested and retry the allocation.
Thanks,
Ming
next prev parent reply other threads:[~2019-01-15 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 1:31 [PATCH] PCI/MSI: preference to returning -ENOSPC from pci_alloc_irq_vectors_affinity Ming Lei
2019-01-14 23:23 ` Bjorn Helgaas
2019-01-15 13:11 ` Christoph Hellwig
2019-01-15 16:22 ` Jens Axboe
2019-01-15 19:31 ` Bjorn Helgaas
2019-01-15 22:46 ` Ming Lei [this message]
2019-01-15 23:49 ` Bjorn Helgaas
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=20190115224631.GA22558@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox