From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for 5.10
Date: Thu, 5 Nov 2020 08:56:04 +0100 [thread overview]
Message-ID: <20201105075604.GA1690984@infradead.org> (raw)
The following changes since commit 65ff5cd04551daf2c11c7928e48fc3483391c900:
blk-mq: mark flush request as IDLE in flush_end_io() (2020-10-30 08:33:49 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.10-2020-11-05
for you to fetch changes up to 0a8a2c85b83589a5c10bc5564b796836bf4b4984:
nvme-tcp: avoid repeated request completion (2020-11-03 10:26:02 +0100)
----------------------------------------------------------------
nvme fixes for 5.10:
- revert a nvme_queue size optimization (Keith Bush)
- fabrics timeout races fixes (Chao Leng and Sagi Grimberg)
----------------------------------------------------------------
Chao Leng (3):
nvme: introduce nvme_sync_io_queues
nvme-rdma: avoid race between time out and tear down
nvme-tcp: avoid race between time out and tear down
Keith Busch (1):
Revert "nvme-pci: remove last_sq_tail"
Sagi Grimberg (2):
nvme-rdma: avoid repeated request completion
nvme-tcp: avoid repeated request completion
drivers/nvme/host/core.c | 8 ++++++--
drivers/nvme/host/nvme.h | 1 +
drivers/nvme/host/pci.c | 23 +++++++++++++++++++----
drivers/nvme/host/rdma.c | 14 +++-----------
drivers/nvme/host/tcp.c | 16 ++++------------
5 files changed, 33 insertions(+), 29 deletions(-)
next reply other threads:[~2020-11-05 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 7:56 Christoph Hellwig [this message]
2020-11-05 14:11 ` [GIT PULL] nvme fixes for 5.10 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2020-11-19 7:50 Christoph Hellwig
2020-11-19 16:23 ` Jens Axboe
2020-10-29 14:49 Christoph Hellwig
2020-10-29 14:54 ` 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=20201105075604.GA1690984@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).