Re: [Xen-devel] Xen 4.2 Release Plan / TODO

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 19.03.12 at 11:57, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>       * file:// backend performance. qemu-xen-tradition's qdisk is quite
>         slow & blktap2 not available in upstream kernels. Need to
>         consider our options:
>               * qemu-xen's qdisk is thought to be well performing but
>                 qemu-xen is not yet the default. Complexity arising from
>                 splitting qemu-for-qdisk out from qemu-for-dm and
>                 running N qemu's.
>               * potentially fully userspace blktap could be ready for
>                 4.2
>               * use /dev/loop+blkback. This requires loop driver AIO and
>                 O_DIRECT patches which are not (AFAIK) yet upstream.

I meant to ask already when this was first mentioned: What's the
reason for this requirement? Didn't we have blkback over loop running
fine for years? Or is this just a performance consideration (in which
case "requires" might be too strong a term)?

Jan

>               * Leverage XCP's blktap2 DKMS work.
>               * Other ideas?



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel