Re: [Xen-devel] RFC: blktap3

[Thanos Makatos <thanos.makatos@xxxxxxxxxx>]

This code was not implemented by me, it was handed over to me in order to 
release it and maintain it. I would really like to have the time to read and 
understand it to be able to address review comments as you said, but my 
allocated time for blktap3 isn't enough for this. My big problem is that code 
in libxl keeps evolving and renders blktap3 code out of sync, and it's a pain 
to rebase it. So, I wanted to see if it was possible to incorporate to 
xen-unstable ASAP, avoiding the rebase effort. I'll be now dividing the code 
into pieces and send it in individual patches, so I believe I'll get a better 
understanding of the code during this process.

-----Original Message-----
From: Jan Beulich [mailto:JBeulich@xxxxxxxx] 
Sent: 10 August 2012 14:12
To: Thanos Makatos
Cc: Goncalo Gomes; xen-devel@xxxxxxxxxxxxx
Subject: Re: [Xen-devel] RFC: blktap3

>>> On 10.08.12 at 13:06, Thanos Makatos <thanos.makatos@xxxxxxxxxx> wrote:
> I haven't yet looked at the code in depth,

How come you post this not insignificant amount of code then?
You ought to be able to address review comments...

Jan

> but I suppose blktap3 can, in some
> cases, be faster than blktap2 since the dom0 kernel doesn't 
> participate in the data path. At least that's what I'd expect ;-).



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