From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme updates for 4.20
Date: Fri, 5 Oct 2018 08:16:07 -0600 [thread overview]
Message-ID: <b5d89dba-8926-1a89-bb8e-d244c425b443@kernel.dk> (raw)
In-Reply-To: <20181005134104.GA11359@infradead.org>
On 10/5/18 7:41 AM, Christoph Hellwig wrote:
> 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(-)
Pulled, thanks.
--
Jens Axboe
prev parent reply other threads:[~2018-10-05 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 13:41 [GIT PULL] nvme updates for 4.20 Christoph Hellwig
2018-10-05 14:16 ` Jens Axboe [this message]
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=b5d89dba-8926-1a89-bb8e-d244c425b443@kernel.dk \
--to=axboe@kernel.dk \
/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