TC leads, please schedule a vote on resolving this issue Fixes: https://github.com/oasis-tcs/virtio-spec/issues/97
Thanks, - Enrico On Mon, Mar 1, 2021 at 11:21 AM Stefan Hajnoczi <[email protected]> wrote: > > On Mon, Mar 01, 2021 at 10:51:03AM -0700, Enrico Granata 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]> > > --- > > content.tex | 31 +++++++++++++++++++++++++++++-- > > 1 file changed, 29 insertions(+), 2 deletions(-) > > Great, please request a Technical Committee vote: > https://github.com/oasis-tcs/virtio-spec/#use-of-github-issues > > Reviewed-by: Stefan Hajnoczi <[email protected]> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
