From: Klaus Jensen <its@irrelevant.dk>
To: Jesper Devantier <jwd@defmacro.it>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Keith Busch" <kbusch@kernel.org>,
qemu-block@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Fam Zheng" <fam@euphon.net>, "Hanna Reitz" <hreitz@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Jesper Wendel Devantier" <j.devantier@samsung.com>
Subject: Re: [PATCH v3 0/5] Support Flexible Data Placement (FDP)
Date: Mon, 6 Mar 2023 14:32:54 +0100 [thread overview]
Message-ID: <ZAXrhqU01mg9vBMx@cormorant.local> (raw)
In-Reply-To: <20230220115926.54623-1-jwd@defmacro.it>
[-- Attachment #1: Type: text/plain, Size: 2251 bytes --]
On Feb 20 12:59, Jesper Devantier wrote:
> 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.
>
> Changelog:
> ==========
>
> * v2 -> v3:
> - remove unused trace points (Keith)
> - style nit - place '||' on preceding line (Keith)
> * v1 -> v2:
> - "hw/nvme: add fleible...": check that max 128 placement handles
> are being created (Keith)
> - removed unused NVMe directives struct (Keith)
>
> 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 | 798 ++++++++++++++++++++++++++++++++++++++++++-
> hw/nvme/ns.c | 147 ++++++++
> hw/nvme/nvme.h | 92 ++++-
> hw/nvme/subsys.c | 94 ++++-
> hw/nvme/trace-events | 1 +
> include/block/nvme.h | 236 ++++++++++++-
> 6 files changed, 1341 insertions(+), 27 deletions(-)
>
Thanks,
applied to nvme-next.
I took the liberty of fixing up the commit message and adding the
missing DIV_ROUND_UP()'s.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-03-06 13:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 11:59 [PATCH v3 0/5] Support Flexible Data Placement (FDP) Jesper Devantier
2023-02-20 11:59 ` [PATCH v3 1/5] hw/nvme: move adjustment of data_units{read,written} Jesper Devantier
2023-02-24 8:20 ` Joel Granados
2023-02-24 9:34 ` Klaus Jensen
2023-02-20 11:59 ` [PATCH v3 2/5] hw/nvme: store a pointer to the NvmeSubsystem in the NvmeNamespace Jesper Devantier
2023-02-20 11:59 ` [PATCH v3 3/5] hw/nvme: add basic endurance group support Jesper Devantier
[not found] ` <CGME20230224085102eucas1p1d57ca7e6909c74db00799be1cff4d9d6@eucas1p1.samsung.com>
2023-02-24 8:51 ` Joel Granados
2023-02-24 9:32 ` Klaus Jensen
2023-02-20 11:59 ` [PATCH v3 4/5] hw/nvme: basic directives support Jesper Devantier
2023-02-20 11:59 ` [PATCH v3 5/5] hw/nvme: flexible data placement emulation Jesper Devantier
2023-03-06 13:32 ` Klaus Jensen [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=ZAXrhqU01mg9vBMx@cormorant.local \
--to=its@irrelevant.dk \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=j.devantier@samsung.com \
--cc=jwd@defmacro.it \
--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).