From: Daniel Wagner <dwagner@suse.de>
To: Keith Busch <kbusch@kernel.org>
Cc: sagi@grimberg.me,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-nvme@lists.infradead.org, ming.lei@redhat.com,
tglx@linutronix.de, hch@lst.de
Subject: Re: [PATCHv3 1/4] nvme/pci: Disable interrupts for threaded handler
Date: Tue, 10 Dec 2019 18:11:34 +0100 [thread overview]
Message-ID: <20191210171134.mpuegw5ainp5kmgg@beryllium.lan> (raw)
In-Reply-To: <20191210165704.GB4424@redsun51.ssa.fujisawa.hgst.com>
On Wed, Dec 11, 2019 at 01:57:04AM +0900, Keith Busch wrote:
> On Tue, Dec 10, 2019 at 05:44:56PM +0100, Daniel Wagner wrote:
> > Sure, I am just a bit confused how IRQ_NONE is used. The comment on
> > nvme_cqe_pending says "We read the CQE phase first to check if the
> > rest of the entry is valid", which I read as "check if we have
> > anything to do" and not "this irq doesn't belong to this queue".
>
> Those two interpretations sound like the same thing to me. :)
:)
I was confused why 'nothing to do' is then interpreted as IRQ was
routed wrongly.
> The interrupt notifies the driver it has something to do, and reading
> the CQE phase confirms whether or not that's true.
I think the thing I am missing the design idea behind it. I suppose the
IRQ on only fires when previously work was posted.
Sorry for the noise.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-12-10 17:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 17:56 [PATCHv3 0/4] nvme pci interrupt handling improvements Keith Busch
2019-12-09 17:56 ` [PATCHv3 1/4] nvme/pci: Disable interrupts for threaded handler Keith Busch
2019-12-10 15:12 ` Daniel Wagner
2019-12-10 15:28 ` Sebastian Andrzej Siewior
2019-12-10 15:54 ` Keith Busch
2019-12-10 16:44 ` Daniel Wagner
2019-12-10 16:57 ` Keith Busch
2019-12-10 17:11 ` Daniel Wagner [this message]
2019-12-12 9:09 ` Christoph Hellwig
2019-12-12 15:53 ` Keith Busch
2019-12-09 17:56 ` [PATCHv3 2/4] nvme/pci: Complete commands from primary handler Keith Busch
2019-12-10 20:00 ` Sagi Grimberg
2019-12-10 20:25 ` Keith Busch
2019-12-10 21:14 ` Sagi Grimberg
2019-12-11 17:35 ` Keith Busch
2019-12-12 0:40 ` Sagi Grimberg
2019-12-12 1:02 ` Keith Busch
2019-12-12 22:55 ` Ming Lei
2019-12-12 23:30 ` Keith Busch
2019-12-13 0:52 ` Ming Lei
2019-12-12 9:14 ` Christoph Hellwig
2019-12-09 17:56 ` [PATCHv3 3/4] nvme/pci: Remove use_threaded_interrupts Keith Busch
2019-12-12 9:14 ` Christoph Hellwig
2019-12-12 15:45 ` Keith Busch
2019-12-18 7:29 ` Ming Lei
2019-12-18 15:50 ` Keith Busch
2019-12-19 1:10 ` Ming Lei
2019-12-09 17:56 ` [PATCHv3 4/4] nvme/pci: Poll threaded completions Keith Busch
2019-12-10 17:43 ` Daniel Wagner
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=20191210171134.mpuegw5ainp5kmgg@beryllium.lan \
--to=dwagner@suse.de \
--cc=bigeasy@linutronix.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.com \
--cc=sagi@grimberg.me \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).