From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: dverkamp@chromium.org, mst@redhat.com,
virtualization@lists.linux-foundation.org,
virtio-dev@lists.linux.dev, oren@nvidia.com, parav@nvidia.com
Subject: Re: [PATCH v2 1/1] virtio-blk: Add description for blk_size field
Date: Wed, 9 Oct 2024 01:46:17 +0300 [thread overview]
Message-ID: <1389ad0b-89b0-4e50-b07d-02bd6141fc7d@nvidia.com> (raw)
In-Reply-To: <20241008201502.GB22682@fedora.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On 08/10/2024 23:15, Stefan Hajnoczi wrote:
> On Sun, Oct 06, 2024 at 07:56:09PM +0300, Max Gurtovoy wrote:
>> This field is only valid when the VIRTIO_BLK_F_BLK_SIZE feature bit is
>> offered by the device.
>>
>> The blk_size field actually represents the logical block size of the
>> device. It is always a power of two and typically ranges from 512 bytes
>> to larger values such as 4 KB.
>>
>> Add description for this field to provide clarity on its constraints.
>>
>> Signed-off-by: Max Gurtovoy<mgurtovoy@nvidia.com>
>> ---
>>
>> changes from V1:
>> - Addressed Stefan's and Daniel's comments:
>> 1. use SHOULD instead of MUST
>> 2. Add a note that devices may return IOERR upon misaligned IO
>> - Add a note that devices may return IOERR if IO size is not following
>> the block size granularity.
>> ---
>> device-types/blk/description.tex | 34 ++++++++++++++++++++++++++++++++
>> 1 file changed, 34 insertions(+)
> Reviewed-by: Stefan Hajnoczi<stefanha@redhat.com>
I'll add both yours and Daniel's Reviewed-by signatures and fix a small
comment from Daniel.
Can you please remind me the next step I should do ?
Should I open an issue at the oasis github and mention it as "Fixes: "
in the commit message ?
[-- Attachment #2: Type: text/html, Size: 2155 bytes --]
next prev parent reply other threads:[~2024-10-08 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 16:56 [PATCH v2 1/1] virtio-blk: Add description for blk_size field Max Gurtovoy
2024-10-08 2:14 ` Daniel Verkamp
2024-10-08 20:15 ` Stefan Hajnoczi
2024-10-08 22:46 ` Max Gurtovoy [this message]
2024-10-09 15:10 ` Stefan Hajnoczi
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=1389ad0b-89b0-4e50-b07d-02bd6141fc7d@nvidia.com \
--to=mgurtovoy@nvidia.com \
--cc=dverkamp@chromium.org \
--cc=mst@redhat.com \
--cc=oren@nvidia.com \
--cc=parav@nvidia.com \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.linux.dev \
--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