From: Jesper Devantier <jwd@defmacro.it>
To: jwd@defmacro.it, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, "Klaus Jensen" <its@irrelevant.dk>,
"Fam Zheng" <fam@euphon.net>, "Keith Busch" <kbusch@kernel.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Jesper Wendel Devantier" <j.devantier@samsung.com>
Subject: [PATCH 0/5] Support Flexible Data Placement (FDP)
Date: Thu, 16 Feb 2023 17:48:01 +0100 [thread overview]
Message-ID: <20230216164806.233533-1-jwd@defmacro.it> (raw)
From: Jesper Wendel Devantier <j.devantier@samsung.com>
Flexible Data Placement (FDP) is a newly introduced enhancement
of the NVM command set introduced by the NVM Express, Inc.
organization as TP 4146. FDP aims to extend the NVM command set
to enable host-guided data placement. FDP-enabled namespaces
can be used as before, but writes may now reference a specific
placement id which in turn points to a reclaim unit (RU). RUs
are defined as some amount of physical, non-volatile storage which
can be erased/reused/repurposed without disturbing any other
reclaim units.
For further details on FDP, consult the specification, which is
available as "TP4146 Flexible Data Placement 2022.11.30 Ratified.pdf"
in the following link:
https://nvmexpress.org/wp-content/uploads/NVM-Express-2.0-Ratified-TPs_20230111.zip
The FDP work builds on 4 preparatory patches, chiefly to add support for
endurance groups and directives.
The final patch adds FDP support itself.
Gollu Appalanaidu (1):
hw/nvme: basic directives support
Jesper Devantier (1):
hw/nvme: flexible data placement emulation
Joel Granados (1):
hw/nvme: move adjustment of data_units{read,written}
Klaus Jensen (1):
hw/nvme: add basic endurance group support
Niklas Cassel (1):
hw/nvme: store a pointer to the NvmeSubsystem in the NvmeNamespace
hw/nvme/ctrl.c | 803 ++++++++++++++++++++++++++++++++++++++++++-
hw/nvme/ns.c | 145 ++++++++
hw/nvme/nvme.h | 92 ++++-
hw/nvme/subsys.c | 94 ++++-
hw/nvme/trace-events | 5 +
include/block/nvme.h | 241 ++++++++++++-
6 files changed, 1353 insertions(+), 27 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-16 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 16:48 Jesper Devantier [this message]
2023-02-16 16:48 ` [PATCH 1/5] hw/nvme: move adjustment of data_units{read,written} Jesper Devantier
2023-02-16 16:48 ` [PATCH 2/5] hw/nvme: store a pointer to the NvmeSubsystem in the NvmeNamespace Jesper Devantier
2023-02-16 16:48 ` [PATCH 3/5] hw/nvme: add basic endurance group support Jesper Devantier
2023-02-16 16:48 ` [PATCH 4/5] hw/nvme: basic directives support Jesper Devantier
2023-02-16 17:23 ` Keith Busch
2023-02-16 17:35 ` Klaus Jensen
2023-02-16 18:02 ` Keith Busch
2023-02-16 16:48 ` [PATCH 5/5] hw/nvme: flexible data placement emulation Jesper Devantier
2023-02-16 18:26 ` Keith Busch
2023-02-16 18:36 ` Jesper Devantier
2023-02-16 19:32 ` Keith Busch
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=20230216164806.233533-1-jwd@defmacro.it \
--to=jwd@defmacro.it \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=its@irrelevant.dk \
--cc=j.devantier@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).