From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] libxl: prefer qdisk over blktap when choosing disk backend
Date: Wed, 28 Aug 2013 15:16:23 +0200 [thread overview]
Message-ID: <521DF827.4000800@m2r.biz> (raw)
In-Reply-To: <21021.62804.505685.545182@mariner.uk.xensource.com>
Il 28/08/2013 15:04, Ian Jackson ha scritto:
> Fabio Fantoni writes ("Re: [Xen-devel] [PATCH] libxl: prefer qdisk over blktap when choosing disk backend"):
>> I think is good prefer qdisk also for significant performance increase
>> in comparison with blktap2.
> Thanks, that's useful information. That, and what George said, have
> convinced me this is the right change.
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
What about qemu traditional with this patch?
I haven't tested qdisk with qemu traditional but unfortunately
qemu-trad. is still widely used and therefore you have to be sure that
does not cause problems.
I asked about because devices parts seem the same with both qemu but I
not sure about it.
next prev parent reply other threads:[~2013-08-28 13:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 14:22 [PATCH] libxl: prefer qdisk over blktap when choosing disk backend Wei Liu
2013-08-28 9:15 ` Wei Liu
2013-08-28 10:35 ` Ian Jackson
2013-08-28 10:51 ` Wei Liu
2013-08-28 10:59 ` George Dunlap
2013-08-28 11:53 ` Fabio Fantoni
2013-08-28 12:46 ` Wei Liu
2013-08-28 13:04 ` Ian Jackson
2013-08-28 13:16 ` Fabio Fantoni [this message]
2013-08-28 13:35 ` Wei Liu
2013-08-28 13:41 ` Wei Liu
2013-08-28 15:04 ` Roger Pau Monné
2013-08-28 15:22 ` Wei Liu
2013-09-03 16:32 ` Ian Campbell
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=521DF827.4000800@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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.