From: hare@suse.de (Hannes Reinecke)
Subject: [PATCHv2 00/11] nvme: ANA support
Date: Tue, 22 May 2018 11:09:53 +0200 [thread overview]
Message-ID: <20180522091004.39620-1-hare@suse.de> (raw)
Hi all,
here's now the second round of adding ANA support to the nvme subsystem.
It's the combined patchset from hch and me, and I've included
all reviews I've had so far.
There are actually two parts to it:
The first patches update AEN configuration support as ANA relies on AENs to be sent.
So we should better make sure that we have them enabled.
The second part is then the ANA support proper.
As usual, comments and reviews are welcome.
Christoph Hellwig (8):
nvme.h: untangle AEN notice definitions
nvmet: refactor AER handling
nvme.h: add ANA definitions
nvme: add support for the log specific field
nvme: always failover on path or transport errors
nvme: add ANA support
nvmet: add a new nvmet_zero_sgl helper
nvmet: split log page implementation
Hannes Reinecke (3):
nvme: submit AEN event configuration on startup
nvmet: Add AEN configuration support
nvmet: ANA support
drivers/nvme/host/core.c | 390 ++++++++++++++++++++++++++++++++++++----
drivers/nvme/host/lightnvm.c | 2 +-
drivers/nvme/host/multipath.c | 43 ++++-
drivers/nvme/host/nvme.h | 20 ++-
drivers/nvme/target/admin-cmd.c | 247 +++++++++++++++++++------
drivers/nvme/target/configfs.c | 381 +++++++++++++++++++++++++++++++++++++++
drivers/nvme/target/core.c | 120 +++++++++++--
drivers/nvme/target/discovery.c | 49 +++--
drivers/nvme/target/io-cmd.c | 36 ++++
drivers/nvme/target/nvmet.h | 52 ++++++
include/linux/nvme.h | 65 ++++++-
11 files changed, 1275 insertions(+), 130 deletions(-)
--
2.12.3
next reply other threads:[~2018-05-22 9:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 9:09 Hannes Reinecke [this message]
2018-05-22 9:09 ` [PATCHv2 01/11] nvme.h: untangle AEN notice definitions Hannes Reinecke
2018-05-22 9:09 ` [PATCHv2 02/11] nvme: submit AEN event configuration on startup Hannes Reinecke
2018-05-22 10:00 ` Christoph Hellwig
2018-05-22 10:55 ` Hannes Reinecke
2018-05-22 9:09 ` [PATCHv2 03/11] nvmet: refactor AER handling Hannes Reinecke
2018-05-22 9:09 ` [PATCHv2 04/11] nvmet: Add AEN configuration support Hannes Reinecke
2018-05-22 10:01 ` Christoph Hellwig
2018-05-22 10:56 ` Hannes Reinecke
2018-05-22 9:09 ` [PATCHv2 05/11] nvme.h: add ANA definitions Hannes Reinecke
2018-05-22 9:09 ` [PATCHv2 06/11] nvme: add support for the log specific field Hannes Reinecke
2018-05-22 9:10 ` [PATCHv2 07/11] nvme: always failover on path or transport errors Hannes Reinecke
2018-05-25 13:24 ` Christoph Hellwig
2018-05-22 9:10 ` [PATCHv2 08/11] nvme: add ANA support Hannes Reinecke
2018-05-23 11:52 ` Popuri, Sriram
2018-05-23 13:19 ` Hannes Reinecke
2018-05-25 13:31 ` Christoph Hellwig
2018-05-25 13:28 ` Christoph Hellwig
2018-05-25 14:32 ` Hannes Reinecke
2018-05-31 10:21 ` Sagi Grimberg
2018-05-22 9:10 ` [PATCHv2 09/11] nvmet: add a new nvmet_zero_sgl helper Hannes Reinecke
2018-05-22 9:10 ` [PATCHv2 10/11] nvmet: split log page implementation Hannes Reinecke
2018-05-22 9:10 ` [PATCHv2 11/11] nvmet: ANA support Hannes Reinecke
2018-05-22 10:05 ` Christoph Hellwig
2018-05-22 11:05 ` Hannes Reinecke
2018-05-25 13:34 ` Christoph Hellwig
2018-05-31 10:27 ` Sagi Grimberg
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=20180522091004.39620-1-hare@suse.de \
--to=hare@suse.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).