From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Thanos Makatos <thanos.makatos@citrix.com>,
"xs-devel@lists.xenserver.org" <xs-devel@lists.xenserver.org>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"s.munaut@whatever-company.com" <s.munaut@whatever-company.com>
Subject: Re: [xs-devel] blktap3 / tapdisk3 development
Date: Thu, 02 Oct 2014 11:23:57 +0200 [thread overview]
Message-ID: <542D19AD.2040404@m2r.biz> (raw)
In-Reply-To: <2368A3FCF9F7214298E53C823B0A48EC0420E2DD@AMSPEX01CL02.citrite.net>
Il 02/10/2014 10:41, Thanos Makatos ha scritto:
>> It seems upcoming XenServer 6.5 "Creedence" is going to use blktap3 /
>> tapdisk3 after all, so if i understand this correctly blktap3 is being developed
>> "only for XenServer", right?
> Correct, although it shouldn't be too much work for making it work on upstream Xen.
>
>> Many interested persons have been asking on mailing lists and on IRC about
>> the status of blktap3 development.
>> Is it possible for someone from Citrix/XenServer to comment about this?
>>
>> I know there's a blog post about blktap3/tapdisk3 performance
>> (improvements) here:
>> http://xenserver.org/blog/entry/tapdisk3
>>
>> One of the interested developers is CC'd on this email. He has written
>> RBD/Ceph support patch for blktap2, and he's interested in porting that to
>> blktap3/tapdisk3..
>>
>> Also is this the correct repo with latest blktap3/tapdisk3 bits in it?:
>> https://github.com/xapi-project/blktap
> blktap3 is actively developed and is the I/O default data path in XenServer 6.5. The repo you mention is the right one (https://github.com/xapi-project/blktap, git branch "xs64bit", but we'll soon bring the "master" branch up to date. I'd be more than happy to assist you and the developer in porting that patch to blktap3!
Sorry for a my probably stupid question.
Why not use qdisk (that have very good performance, support many formats
and is supported also by other project) and improve it if needed instead
do/maintain another project xen-only?
FWIK the only thing in what blktab is better is vhd support (not vhdx).
Thanks for any reply and sorry for my bad english.
>
> Cheers
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-10-02 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141001181023.GG12451@reaktio.net>
2014-10-02 8:41 ` [xs-devel] blktap3 / tapdisk3 development Thanos Makatos
[not found] ` <2368A3FCF9F7214298E53C823B0A48EC0420E2DD@AMSPEX01CL02.citrite.net>
2014-10-02 9:23 ` Fabio Fantoni [this message]
2014-10-02 15:17 ` Felipe Franciosi
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=542D19AD.2040404@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=s.munaut@whatever-company.com \
--cc=thanos.makatos@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=xs-devel@lists.xenserver.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;
as well as URLs for NNTP newsgroup(s).