From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <fam@euphon.net>,
qemu-block@nongnu.org, Klaus Jensen <k.jensen@samsung.com>,
Gollu Appalanaidu <anaidu.gollu@samsung.com>,
Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH v4 00/12] hw/block/nvme: metadata and end-to-end data protection support
Date: Mon, 8 Mar 2021 12:32:20 +0100 [thread overview]
Message-ID: <YEYLRNv79RGN5J6v@apples.localdomain> (raw)
In-Reply-To: <20210301140047.106261-1-its@irrelevant.dk>
[-- Attachment #1: Type: text/plain, Size: 3131 bytes --]
On Mar 1 15:00, Klaus Jensen wrote:
> From: Klaus Jensen <k.jensen@samsung.com>
>
> This is v4 (RFC removed) of a series that adds support for metadata and
> end-to-end data protection.
>
> First, on the subject of metadata, in v1, support was restricted to
> extended logical blocks, which was pretty trivial to implement, but
> required special initialization and broke DULBE. In v2, metadata is
> always stored continuously at the end of the underlying block device.
> This has the advantage of not breaking DULBE since the data blocks
> remains aligned and allows bdrv_block_status to be used to determinate
> allocation status. It comes at the expense of complicating the extended
> LBA emulation, but on the other hand it also gains support for metadata
> transfered as a separate buffer.
>
> The end-to-end data protection support blew up in terms of required
> changes. This is due to the fact that a bunch of new commands has been
> added to the device since v1 (zone append, compare, copy), and they all
> require various special handling for protection information. If
> potential reviewers would like it split up into multiple patches, each
> adding pi support to one command, shout out.
>
> The core of the series (metadata and eedp) is preceeded by a set of
> patches that refactors mapping (yes, again) and tries to deal with the
> qsg/iov duality mess (maybe also again?).
>
> Support fro metadata and end-to-end data protection is all joint work
> with Gollu Appalanaidu.
>
> v4:
> * promoted from RFC
> * moved most eedp additions to nvme-dif.{c,h}. (Keith)
>
> v3:
>
> * added patch with Verify command
> * added patches for multiple LBA formats and Format NVM
> * changed NvmeSG to be a union (Keith)
>
> Gollu Appalanaidu (1):
> hw/block/nvme: add verify command
>
> Klaus Jensen (9):
> hw/block/nvme: remove redundant len member in compare context
> hw/block/nvme: remove block accounting for write zeroes
> hw/block/nvme: fix strerror printing
> hw/block/nvme: try to deal with the iov/qsg duality
> hw/block/nvme: remove the req dependency in map functions
> hw/block/nvme: refactor nvme_dma
> hw/block/nvme: add metadata support
> hw/block/nvme: end-to-end data protection
> hw/block/nvme: add non-mdts command size limit for verify
>
> Minwoo Im (2):
> hw/block/nvme: support multiple lba formats
> hw/block/nvme: add support for the format nvm command
>
> hw/block/nvme-dif.h | 53 ++
> hw/block/nvme-ns.h | 49 +-
> hw/block/nvme.h | 51 +-
> include/block/nvme.h | 34 +-
> hw/block/nvme-dif.c | 513 ++++++++++++++
> hw/block/nvme-ns.c | 90 ++-
> hw/block/nvme.c | 1548 ++++++++++++++++++++++++++++++++++-------
> hw/block/meson.build | 2 +-
> hw/block/trace-events | 25 +-
> 9 files changed, 2071 insertions(+), 294 deletions(-)
> create mode 100644 hw/block/nvme-dif.h
> create mode 100644 hw/block/nvme-dif.c
>
> --
> 2.30.1
>
Applied patches 1 through 6. I'll let the metadata and eedp patches
simmer for a few days more.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-08 11:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 14:00 [PATCH v4 00/12] hw/block/nvme: metadata and end-to-end data protection support Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 01/12] hw/block/nvme: remove redundant len member in compare context Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 02/12] hw/block/nvme: remove block accounting for write zeroes Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 03/12] hw/block/nvme: fix strerror printing Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 04/12] hw/block/nvme: try to deal with the iov/qsg duality Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 05/12] hw/block/nvme: remove the req dependency in map functions Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 06/12] hw/block/nvme: refactor nvme_dma Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 07/12] hw/block/nvme: add metadata support Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 08/12] hw/block/nvme: end-to-end data protection Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 09/12] hw/block/nvme: add verify command Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 10/12] hw/block/nvme: add non-mdts command size limit for verify Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 11/12] hw/block/nvme: support multiple lba formats Klaus Jensen
2021-03-01 14:00 ` [PATCH v4 12/12] hw/block/nvme: add support for the format nvm command Klaus Jensen
2021-03-01 18:58 ` [PATCH v4 00/12] hw/block/nvme: metadata and end-to-end data protection support Keith Busch
2021-03-08 11: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=YEYLRNv79RGN5J6v@apples.localdomain \
--to=its@irrelevant.dk \
--cc=anaidu.gollu@samsung.com \
--cc=fam@euphon.net \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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).