[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFC v3 00/12] hw/block/nvme: metadata and end-to-end data pro
|
From: |
Keith Busch |
|
Subject: |
Re: [PATCH RFC v3 00/12] hw/block/nvme: metadata and end-to-end data protection support |
|
Date: |
Thu, 18 Feb 2021 02:50:30 +0900 |
|
User-agent: |
Mutt/1.12.1 (2019-06-15) |
On Wed, Feb 17, 2021 at 10:06:49AM +0100, Klaus Jensen wrote:
> On Feb 16 16:19, Keith Busch wrote:
> > The verify implementation looked fine, but lacking a generic backing for
> > it sounds to me the use cases aren't there to justify taking on this
> > feature.
>
> Please check my reply on the verify patch - can you elaborate on
> "generic backing"? I'm not sure I understand what you have in mind,
> API-wise.
I meant it'd be nice if qemu block api provided a function like
"blk_aio_pverify()" to handle the details that you're implementing in
the nvme device. As you mentioned though, handling the protection
information part is problematic.