From: keith.busch@linux.intel.com (Keith Busch)
Subject: nvme: batch completions and do them outside of the queue lock
Date: Wed, 16 May 2018 15:27:57 -0600 [thread overview]
Message-ID: <20180516212757.GD20223@localhost.localdomain> (raw)
In-Reply-To: <528cf765-16ae-5499-8843-9a62b4fd8326@kernel.dk>
On Wed, May 16, 2018@02:37:40PM -0600, Jens Axboe wrote:
> This patch splits up the reaping of completion entries, and the
> block side completion. The advantage of this is two-fold:
>
> 1) We can batch completions, this patch pulls them off in units
> of 8, but that number is fairly arbitrary. I wanted it to be
> big enough to hold most use cases, but not big enough to be
> a stack burden.
>
> 2) We complete the block side of things outside of the queue lock.
Interesting idea. Since you bring this up, I think there may be more
optimizations on top of this concept. I'll stare at this a bit before
applying, or may have a follow-up proposal later.
> Note that this kills the ->cqe_seen as well. I haven't been able
> to trigger any ill effects of this. If we do race with polling
> every so often, it should be rare enough NOT to trigger any issues.
We'll know who to blame if spurious interrupt messages are seen. :)
next prev parent reply other threads:[~2018-05-16 21:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 20:37 nvme: batch completions and do them outside of the queue lock Jens Axboe
2018-05-16 21:27 ` Keith Busch [this message]
2018-05-16 22:35 ` Keith Busch
2018-05-16 22:57 ` Jens Axboe
2018-05-16 23:10 ` Jens Axboe
2018-05-16 23:18 ` Jens Axboe
2018-05-16 23:39 ` Jens Axboe
2018-05-17 2:09 ` Keith Busch
2018-05-17 3:16 ` Jens Axboe
2018-05-17 3:16 ` Jens Axboe
2018-05-17 7:16 ` Christoph Hellwig
2018-05-17 7: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=20180516212757.GD20223@localhost.localdomain \
--to=keith.busch@linux.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 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).