On 18/11/2016 10:51, Alberto Garcia wrote:
>
>>> >> Honestly I don't see the point. It seems easier, more practical and
>>> >> more effective to convert bdrv_aio_* to byte ranges, especially since
>>> >> QED would be basically a rewrite.
>> >
>> > Well, it's an RFC for a reason, I want people
On Fri 11 Nov 2016 11:22:26 AM CET, Kevin Wolf wrote:
>> Honestly I don't see the point. It seems easier, more practical and
>> more effective to convert bdrv_aio_* to byte ranges, especially since
>> QED would be basically a rewrite.
>
> Well, it's an RFC for a reason, I want people to give
Am 11.11.2016 um 10:56 hat Paolo Bonzini geschrieben:
> On 10/11/2016 18:19, Kevin Wolf wrote:
> > This is part of a series that I'm working on and that aims to remove the
> > bdrv_aio_*() emulation in io.c. blkdebug and blkverify were easy, but for
> > quorum I need a few more patches, so I'm
On 10/11/2016 18:19, Kevin Wolf wrote:
> This is part of a series that I'm working on and that aims to remove the
> bdrv_aio_*() emulation in io.c. blkdebug and blkverify were easy, but for
> quorum I need a few more patches, so I'm sending this out as an RFC while I
> continue work on the rest
This is part of a series that I'm working on and that aims to remove the
bdrv_aio_*() emulation in io.c. blkdebug and blkverify were easy, but for
quorum I need a few more patches, so I'm sending this out as an RFC while I
continue work on the rest (QED, and then possibly some polishing).
After