From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Fam Zheng <famz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"open list:GLUSTER" <qemu-block@nongnu.org>,
Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>,
Wen Congyang <wencongyang2@huawei.com>,
Jeff Cody <jcody@redhat.com>, Peter Lieven <pl@kamp.de>,
"Richard W.M. Jones" <rjones@redhat.com>,
Max Reitz <mreitz@redhat.com>,
"open list:Sheepdog" <sheepdog@lists.wpkg.org>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
"Denis V. Lunev" <den@openvz.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Liu Yuan <namei.unix@gmail.com>,
Xie Changlong <xiechanglong.d@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] block: Merge .bdrv_co_writev{, _flags} in drivers
Date: Wed, 25 Apr 2018 09:06:59 +0100 [thread overview]
Message-ID: <20180425080659.GD30024@redhat.com> (raw)
In-Reply-To: <20180424220157.177385-1-eblake@redhat.com>
On Tue, Apr 24, 2018 at 05:01:57PM -0500, Eric Blake wrote:
> We have too many driver callback interfaces; simplify the mess
> somewhat by merging the flags parameter of .bdrv_co_writev_flags()
> into .bdrv_co_writev_flags(). Note that as long as a driver doesn't
Typo - this should be just .bdrv_co_writev
> set .supported_write_flags, the flags argument will be 0 and behavior
> is identical. Also note that the public function bdrv_co_writev()
> still lacks a flags argument; so the driver signature is thus
> intentionally slightly different. But that's not the end of the
> world, nor the first time that the driver interface differs slightly
> from the public interface.
>
> Ideally, we should be rewriting all of these drivers to use modern
> byte-based interfaces. But that's a more invasive patch to write
> and audit, compared to the simplification done here.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>
> Based-on: <20180424192506.149089-1-eblake@redhat.com>
> ([PATCH v2 0/6] block: byte-based AIO read/write)
>
> include/block/block_int.h | 2 --
> block/io.c | 13 ++++---------
> block/gluster.c | 4 +++-
> block/iscsi.c | 8 ++++----
> block/parallels.c | 4 +++-
> block/qcow.c | 6 ++++--
> block/qed.c | 3 ++-
> block/replication.c | 4 +++-
> block/sheepdog.c | 4 +++-
> block/ssh.c | 4 +++-
> block/vhdx.c | 4 +++-
> 11 files changed, 32 insertions(+), 24 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-04-25 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 22:01 [Qemu-devel] [PATCH] block: Merge .bdrv_co_writev{, _flags} in drivers Eric Blake
2018-04-25 8:06 ` Daniel P. Berrangé [this message]
2018-04-25 11:15 ` Kevin Wolf
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=20180425080659.GD30024@redhat.com \
--to=berrange@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=mreitz@redhat.com \
--cc=namei.unix@gmail.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=ronniesahlberg@gmail.com \
--cc=sheepdog@lists.wpkg.org \
--cc=stefanha@redhat.com \
--cc=wencongyang2@huawei.com \
--cc=xiechanglong.d@gmail.com \
/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).