From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <keith.busch@intel.com>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Date: Fri, 5 Oct 2018 15:39:53 +0200 [thread overview]
Message-ID: <20181005133953.GA11305@infradead.org> (raw)
Bcc:
Subject: [GIT PULL] nvme updates for 4.20
Reply-To:
A relatively boring merge window:
- better AEN tracing (Chaitanya)
- NUMA aware PCIe multipathing (me)
- RDMA workqueue fixes (Sagi)
- better bio usage in the target (Sagi)
- FC rework for target removal (James)
- better multipath handling of ->queue_rq failures (James)
- various cleanups (Milan)
The following changes since commit c0aac682fa6590cb660cb083dbc09f55e799d2d2:
Merge tag 'v4.19-rc6' into for-4.20/block (2018-10-01 08:58:57 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-4.20
for you to fetch changes up to 2acf70ade79d26b97611a8df52eb22aa33814cd4:
nvmet-rdma: use a private workqueue for delete (2018-10-05 09:25:18 +0200)
----------------------------------------------------------------
Chaitanya Kulkarni (2):
nvmet: remove redundant module prefix
nvme-core: add async event trace helper
Christoph Hellwig (1):
nvme: take node locality into account when selecting a path
James Smart (3):
nvmet_fc: support target port removal with nvmet layer
nvme_fc: add 'nvme_discovery' sysfs attribute to fc transport device
nvme: call nvme_complete_rq when nvmf_check_ready fails for mpath I/O
Milan P. Gandhi (2):
nvme: fix typo in nvme_identify_ns_descs
nvme-fc: fix for a minor typos
Sagi Grimberg (2):
nvmet: don't split large I/Os unconditionally
nvmet-rdma: use a private workqueue for delete
drivers/nvme/host/core.c | 20 ++++--
drivers/nvme/host/fabrics.c | 7 +-
drivers/nvme/host/fc.c | 108 +++++++++++++++++++++++++++----
drivers/nvme/host/multipath.c | 57 +++++++++++++----
drivers/nvme/host/nvme.h | 25 +++-----
drivers/nvme/host/trace.h | 28 ++++++++
drivers/nvme/target/admin-cmd.c | 2 +-
drivers/nvme/target/fc.c | 130 +++++++++++++++++++++++++++++++++++---
drivers/nvme/target/io-cmd-bdev.c | 9 ++-
drivers/nvme/target/nvmet.h | 1 +
drivers/nvme/target/rdma.c | 19 ++++--
include/linux/nvme.h | 1 +
12 files changed, 347 insertions(+), 60 deletions(-)
reply other threads:[~2018-10-05 20:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181005133953.GA11305@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--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).