From: "Roger Pau Monné" <roger.pau@citrix.com>
To: paul@xen.org
Cc: Anthony PERARD <anthony.perard@vates.tech>,
xen-devel@lists.xenproject.org, Owen Smith <owen.smith@cloud.com>,
Mark Syms <mark.syms@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Juergen Gross <jgross@suse.com>
Subject: Re: Block protocol incompatibilities with 4K logical sector size disks
Date: Mon, 2 Sep 2024 17:23:37 +0200 [thread overview]
Message-ID: <ZtXYeaKp-ug8oFjX@macbook.local> (raw)
In-Reply-To: <13d84592-64c5-4e34-93be-3f8ecb7afb15@xen.org>
On Mon, Sep 02, 2024 at 03:19:56PM +0100, Paul Durrant wrote:
> On 02/09/2024 09:55, Roger Pau Monné wrote:
> [snip]
> >
> > Thanks for your input. I would also like to hear from the blktap and
> > Windows PV drivers maintainers, as the change that I'm proposing here
> > will require changes to their implementations.
> >
>
> So IIUC you are proposing to refuse to connect to a frontend that sets
> feature-large-sector-size if sector-size != 512? Is that right?
Is is worth retrofitting this into existing backends? My suggestion
would be to make `feature-large-sector-size` not mandatory to expose a
sector-size != 512, but I wouldn't go as far as refusing to connect to
frontends that expose the feature. I have no idea which frontends
might expose `feature-large-sector-size` but still be compatible with
Linux blkback regarding sector-size != 512 (I know the Windows one
isn't).
I think we have reached consensus with Anthony on the approach, so it
might be best if I just draft a proposal change to blkif.h because
that's less ambiguous than attempting to describe it here.
Thanks, Roger.
next prev parent reply other threads:[~2024-09-02 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 10:59 Block protocol incompatibilities with 4K logical sector size disks Roger Pau Monné
2024-08-29 13:15 ` Anthony PERARD
2024-08-29 15:42 ` Roger Pau Monné
2024-08-30 16:09 ` Anthony PERARD
2024-09-02 8:55 ` Roger Pau Monné
2024-09-02 14:19 ` Paul Durrant
2024-09-02 15:23 ` Roger Pau Monné [this message]
2024-09-02 15:25 ` Paul Durrant
2024-09-02 15:50 ` Anthony PERARD
2024-09-02 16:08 ` Roger Pau Monné
2024-09-02 14:50 ` Mark Syms
2024-09-02 15:26 ` Roger Pau Monné
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=ZtXYeaKp-ug8oFjX@macbook.local \
--to=roger.pau@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jgross@suse.com \
--cc=mark.syms@citrix.com \
--cc=owen.smith@cloud.com \
--cc=paul@xen.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.