From: Anthony PERARD <anthony.perard@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: qemu-devel@nongnu.org, xen-devel@lists.xensource.com,
kraxel@redhat.com, sstabellini@kernel.org
Subject: Re: [Qemu-devel] [PATCH] xen: use native disk xenbus protocol if possible
Date: Wed, 29 Jun 2016 16:20:00 +0100 [thread overview]
Message-ID: <20160629152000.GA5666@perard.uk.xensource.com> (raw)
In-Reply-To: <1466162096-4934-1-git-send-email-jgross@suse.com>
On Fri, Jun 17, 2016 at 01:14:56PM +0200, Juergen Gross wrote:
> The qdisk implementation is using the native xenbus protocol only in
> case of no protocol specified at all. As using the explicit 32- or
> 64-bit protocol is slower than the native one due to copying requests
> not by memcpy but element for element, this is not optimal.
>
> Correct this by using the native protocol in case word sizes of
> frontend and backend match.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> hw/block/xen_disk.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/hw/block/xen_disk.c b/hw/block/xen_disk.c
> index 2862b59..0961fcb 100644
> --- a/hw/block/xen_disk.c
> +++ b/hw/block/xen_disk.c
> @@ -976,14 +976,14 @@ static int blk_connect(struct XenDevice *xendev)
> blkdev->feature_persistent = !!pers;
> }
>
> - blkdev->protocol = BLKIF_PROTOCOL_NATIVE;
> - if (blkdev->xendev.protocol) {
> - if (strcmp(blkdev->xendev.protocol, XEN_IO_PROTO_ABI_X86_32) == 0) {
> - blkdev->protocol = BLKIF_PROTOCOL_X86_32;
> - }
> - if (strcmp(blkdev->xendev.protocol, XEN_IO_PROTO_ABI_X86_64) == 0) {
> - blkdev->protocol = BLKIF_PROTOCOL_X86_64;
> - }
> + if (!blkdev->xendev.protocol) {
> + blkdev->protocol = BLKIF_PROTOCOL_NATIVE;
> + } else if (strcmp(blkdev->xendev.protocol, XEN_IO_PROTO_ABI_NATIVE) == 0) {
> + blkdev->protocol = BLKIF_PROTOCOL_NATIVE;
> + } else if (strcmp(blkdev->xendev.protocol, XEN_IO_PROTO_ABI_X86_32) == 0) {
> + blkdev->protocol = BLKIF_PROTOCOL_X86_32;
> + } else if (strcmp(blkdev->xendev.protocol, XEN_IO_PROTO_ABI_X86_64) == 0) {
> + blkdev->protocol = BLKIF_PROTOCOL_X86_64;
There is one difference with the previous code, in case the protocol is
specified, but it not x86_32 or x86_64, then no blkdev->protocol is
selected (then no ring is initialized). Could you re-add this case?
--
Anthony PERARD
next prev parent reply other threads:[~2016-06-29 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 11:14 [Qemu-devel] [PATCH] xen: use native disk xenbus protocol if possible Juergen Gross
2016-06-27 10:54 ` [Qemu-devel] [Xen-devel] " Juergen Gross
2016-06-29 15:20 ` Anthony PERARD [this message]
2016-06-29 15:38 ` [Qemu-devel] " Juergen Gross
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=20160629152000.GA5666@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=jgross@suse.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xensource.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).