From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Alvaro Karsz <alvaro.karsz@solid-run.com>,
virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org, dm-devel@redhat.com,
linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org,
Jason Wang <jasowang@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Enrico Granata <egranata@google.com>
Subject: Re: [PATCH v3] virtio_blk: add VIRTIO_BLK_F_LIFETIME feature support
Date: Mon, 5 Dec 2022 15:29:02 -0500 [thread overview]
Message-ID: <20221205152708-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <23c98c7c-3ed0-0d26-24c0-ed8a63266dcc@kernel.dk>
On Mon, Dec 05, 2022 at 11:53:51AM -0700, Jens Axboe wrote:
> On 12/5/22 11:36 AM, Alvaro Karsz wrote:
> > Hi,
> >
> >> Is this based on some spec? Because it looks pretty odd to me. There
> >> can be a pretty wide range of two/three/etc level cells with wildly
> >> different ranges of durability. And there's really not a lot of slc
> >> for generic devices these days, if any.
> >
> > Yes, this is based on the virtio spec
> > https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01.html
> > section 5.2.6
>
> And where did this come from?
Here's the commit log from the spec:
In many embedded systems, virtio-blk implementations are
backed by eMMC or UFS storage devices, which are subject to
predictable and measurable wear over time due to repeated write
cycles.
For such systems, it can be important to be able to track
accurately the amount of wear imposed on the storage over
time and surface it to applications. In a native deployments
this is generally handled by the physical block device driver
but no such provision is made in virtio-blk to expose these
metrics for devices where it makes sense to do so.
This patch adds support to virtio-blk for lifetime and wear
metrics to be exposed to the guest when a deployment of
virtio-blk is done over compatible eMMC or UFS storage.
Signed-off-by: Enrico Granata <egranata@google.com>
Cc Enrico Granata as well.
> --
> Jens Axboe
>
next prev parent reply other threads:[~2022-12-05 20:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 16:20 [PATCH v3] virtio_blk: add VIRTIO_BLK_F_LIFETIME feature support Alvaro Karsz
2022-12-05 18:24 ` Jens Axboe
2022-12-05 18:36 ` Alvaro Karsz
2022-12-05 18:53 ` Jens Axboe
2022-12-05 20:29 ` Michael S. Tsirkin [this message]
2022-12-05 20:35 ` Enrico Granata
2022-12-05 23:09 ` Chaitanya Kulkarni
2022-12-05 20:36 ` Jens Axboe
2022-12-05 22:28 ` Chaitanya Kulkarni
2022-12-05 18:25 ` Jens Axboe
2022-12-06 16:31 ` Stefan Hajnoczi
2022-12-06 16:40 ` Michael S. Tsirkin
2022-12-06 18:25 ` Alvaro Karsz
2022-12-06 18:43 ` Bart Van Assche
2022-12-06 19:56 ` Alvaro Karsz
2022-12-07 3:32 ` Chaitanya Kulkarni
2022-12-07 7:35 ` Christoph Hellwig
2022-12-07 10:21 ` Michael S. Tsirkin
2022-12-07 16:31 ` Christoph Hellwig
2022-12-07 20:28 ` Michael S. Tsirkin
2022-12-11 9:49 ` Alvaro Karsz
2022-12-13 4:59 ` Chaitanya Kulkarni
2022-12-13 4:58 ` Chaitanya Kulkarni
2022-12-13 6:23 ` Michael S. Tsirkin
2022-12-19 7:59 ` Michael S. Tsirkin
2022-12-19 8:39 ` Alvaro Karsz
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=20221205152708-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=egranata@google.com \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.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 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).