Please do start a vote on this issue at your earliest convenience Fixes: https://github.com/oasis-tcs/virtio-spec/issues/97
Thanks, - Enrico On Mon, Mar 15, 2021 at 5:27 AM Cornelia Huck <[email protected]> wrote: > > On Tue, 9 Mar 2021 14:20:14 -0700 > Enrico Granata <[email protected]> wrote: > > > 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 <[email protected]> > > Fixes: https://github.org/oasis-tcs/virtio-spec/issues/97 > > --- > > content.tex | 35 +++++++++++++++++++++++++++++++++-- > > 1 file changed, 33 insertions(+), 2 deletions(-) > > > > diff --git a/content.tex b/content.tex > > index b72bad0..75631ba 100644 > > --- a/content.tex > > +++ b/content.tex > > @@ -4418,6 +4418,9 @@ \subsection{Feature bits}\label{sec:Device Types > > / Block Device / Feature bits} > > There still seems to be something wrong with the line wrapping in this > patch (won't apply without manual massaging) -- can you please > double-check your setup? > > That said, I think we can still vote on this patch; please add the link > to this version to the github issue if you think it's time for voting. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
