From: Cornelia Huck <cohuck@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>,
Enrico Granata <egranata@google.com>
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] Fwd: [PATCH v2] Provide detailed specification of virtio-blk lifetime metrics
Date: Wed, 14 Jul 2021 11:36:58 +0200 [thread overview]
Message-ID: <87pmvlck3p.fsf@redhat.com> (raw)
In-Reply-To: <YO6ro345FI0XE8vv@stefanha-x1.localdomain>
On Wed, Jul 14 2021, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> On Wed, May 05, 2021 at 12:37:26PM -0700, Enrico Granata wrote:
>> ---------- Forwarded message ---------
>> From: Enrico Granata <egranata@google.com>
>> Date: Wed, May 5, 2021 at 1:37 PM
>> Subject: [PATCH v2] Provide detailed specification of virtio-blk
>> lifetime metrics
>> To: <virtio-dev@lists.oasis-open.org>
>> Cc: <egranata@google.com>, <hch@infradead.org>, <mst@redhat.com>,
>> <linux-block@vger.kernel.org>,
>> <virtualization@lists.linux-foundation.org>
>>
>>
>> In the course of review, some concerns were surfaced about the
>> original virtio-blk lifetime proposal, as it depends on the eMMC
>> spec which is not open
>>
>> Add a more detailed description of the meaning of the fields
>> added by that proposal to the virtio-blk specification, as to
>> make it feasible to understand and implement the new lifetime
>> metrics feature without needing to refer to JEDEC's specification
>>
>> This patch does not change the meaning of those fields nor add
>> any new fields, but it is intended to provide an open and more
>> clear description of the meaning associated with those fields.
>>
>> Signed-off-by: Enrico Granata <egranata@google.com>
>> ---
>> Changes in v2:
>> - clarified JEDEC references;
>> - added VIRTIO_BLK prefix and cleaned up comment syntax;
>> - clarified reserved block references
>>
>> content.tex | 40 ++++++++++++++++++++++++++++++++--------
>> 1 file changed, 32 insertions(+), 8 deletions(-)
>
> Ping?
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[Enrico is currently on leave of absence]
Is there any outstanding feedback from the linux-block folks? I've lost
track of this, I'm afraid. (Your R-b is the only feedback I see on this
list...)
We can certainly put up a vote. This is one of the things I wanted to
see fixed for the next release of the standard.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2021-07-14 9:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 19:36 [PATCH v2] Provide detailed specification of virtio-blk lifetime metrics Enrico Granata
2021-05-05 19:37 ` [virtio-dev] Fwd: " Enrico Granata
2021-05-17 10:33 ` Cornelia Huck
2021-05-17 15:55 ` Enrico Granata
2021-05-24 16:48 ` Enrico Granata
2021-07-14 9:17 ` Stefan Hajnoczi
2021-07-14 9:36 ` Cornelia Huck [this message]
2021-07-14 14:25 ` Stefan Hajnoczi
2021-07-14 14:25 ` Stefan Hajnoczi
2021-08-06 19:19 ` Enrico Granata
2021-10-06 11:54 ` Cornelia Huck
2021-10-06 11:54 ` Cornelia Huck
2021-10-06 11:54 ` Cornelia Huck
2021-10-06 15:58 ` Enrico Granata
2021-10-14 15:37 ` Cornelia Huck
2021-10-14 15:37 ` Cornelia Huck
2021-10-14 15:37 ` Cornelia Huck
2021-10-14 19:00 ` Enrico Granata
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=87pmvlck3p.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=egranata@google.com \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.