From: hch@lst.de (Christoph Hellwig)
Subject: RFC: handle completions outside the queue lock and split the queue lock
Date: Thu, 17 May 2018 19:00:45 +0200 [thread overview]
Message-ID: <20180517170045.GA4945@lst.de> (raw)
In-Reply-To: <20180517165546.GE23555@localhost.localdomain>
On Thu, May 17, 2018@10:55:46AM -0600, Keith Busch wrote:
> On Thu, May 17, 2018@06:31:45PM +0200, Christoph Hellwig wrote:
> > Mostly the previous work from Jens, just with random cleanups from me
> > thrown in. Based on nvme/nvme-4.18 minus the two top-most commits,
> > very lightly tested.
>
> Looking good. I can force push a rebase removing the current top-two
> commits. Sound okay?
Yes, let's do that for now, and let pending series settle for another
day or two.
next prev parent reply other threads:[~2018-05-17 17:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 16:31 RFC: handle completions outside the queue lock and split the queue lock Christoph Hellwig
2018-05-17 16:31 ` [PATCH 1/7] nvme: mark the result argument to nvme_complete_async_event volatile Christoph Hellwig
2018-05-17 16:31 ` [PATCH 2/7] nvme-pci: simplify nvme_cqe_valid Christoph Hellwig
2018-05-17 16:31 ` [PATCH 3/7] nvme-pci: remove cq check after submission Christoph Hellwig
2018-05-17 16:31 ` [PATCH 4/7] nvme-pci: move ->cq_vector == -1 check outside of ->q_lock Christoph Hellwig
2018-05-17 16:31 ` [PATCH 5/7] nvme-pci: handle completions outside of the queue lock Christoph Hellwig
2018-05-17 16:31 ` [PATCH 6/7] nvme-pci: split the nvme queue lock into submission and completion locks Christoph Hellwig
2018-05-17 16:31 ` [PATCH 7/7] nvme-pci: drop IRQ disabling on submission queue lock Christoph Hellwig
2018-05-17 16:36 ` RFC: handle completions outside the queue lock and split the " Jens Axboe
2018-05-17 16:44 ` Christoph Hellwig
2018-05-17 16:55 ` Keith Busch
2018-05-17 17:00 ` Christoph Hellwig [this message]
2018-05-17 17:05 ` Keith Busch
2018-05-17 17:08 ` Jens Axboe
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=20180517170045.GA4945@lst.de \
--to=hch@lst.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).