From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: Jens Axboe <axboe@kernel.dk>, Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v3] virtio_blk: add SECURE ERASE command support
Date: Thu, 29 Sep 2022 03:20:51 -0400 [thread overview]
Message-ID: <20220929032021-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJs=3_CmKjhS=Y3JHujws9y5KmN-AbSRXTnt1aZOhDzMuK7g3Q@mail.gmail.com>
On Thu, Sep 29, 2022 at 10:13:47AM +0300, Alvaro Karsz wrote:
> > Could you explain this last part? Why are they used without
> > VIRTIO_BLK_F_DISCARD?
>
>
> Sure,
>
> If both VIRTIO_BLK_F_DISCARD and VIRTIO_BLK_F_SECURE_ERASE are negotiated:
> q->limits.max_discard_segments =
> min(virtio_blk_config->max_discard_seg,
> virtio_blk_config->max_secure_erase_seg)
>
> If VIRTIO_BLK_F_DISCARD is negotiated and VIRTIO_BLK_F_SECURE_ERASE isn't
> q->limits.max_discard_segments = virtio_blk_config->max_discard_seg
>
> If VIRTIO_BLK_F_SECURE_ERASE is negotiated and VIRTIO_BLK_F_DISCARD isn't
> q->limits.max_discard_segments = virtio_blk_config->max_secure_erase_seg
OK so virtio_blk_config->max_discard_seg is unused without
VIRTIO_BLK_F_DISCARD.
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-09-29 7:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 8:27 [PATCH v3] virtio_blk: add SECURE ERASE command support Alvaro Karsz
2022-09-22 17:45 ` Stefan Hajnoczi
2022-09-28 10:48 ` Alvaro Karsz
2022-09-28 13:15 ` Michael S. Tsirkin
2022-09-29 7:13 ` Alvaro Karsz
2022-09-29 7:20 ` Michael S. Tsirkin [this message]
2022-09-29 7:29 ` Alvaro Karsz
2022-09-29 7:45 ` Michael S. Tsirkin
2022-09-29 8:51 ` Alvaro Karsz
2022-10-07 13:12 ` Michael S. Tsirkin
2022-10-08 4:48 ` Jason Wang
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=20220929032021-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=axboe@kernel.dk \
--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).