Re: [Qemu-devel] [PATCH 02/20] blockjob: introduce .drain callback for jobs

2016-12-03 Thread Paolo Bonzini
, 2016 3:01:30 PM > Subject: Re: [Qemu-devel] [PATCH 02/20] blockjob: introduce .drain callback > for jobs > > 27.10.2016 13:48, Paolo Bonzini wrote: > > This is required to decouple block jobs from running in an > > AioContext. With multiqueue block devices,

Re: [Qemu-devel] [PATCH 02/20] blockjob: introduce .drain callback for jobs

2016-12-02 Thread Vladimir Sementsov-Ogievskiy
27.10.2016 13:48, Paolo Bonzini wrote: This is required to decouple block jobs from running in an AioContext. With multiqueue block devices, a BlockDriverState does not really belong to a single AioContext. The solution is to first wait until all I/O operations are complete; then loop in the

[Qemu-devel] [PATCH 02/20] blockjob: introduce .drain callback for jobs

2016-10-27 Thread Paolo Bonzini
This is required to decouple block jobs from running in an AioContext. With multiqueue block devices, a BlockDriverState does not really belong to a single AioContext. The solution is to first wait until all I/O operations are complete; then loop in the main thread for the block job to complete

[Qemu-devel] [PATCH 02/20] blockjob: introduce .drain callback for jobs

2016-10-17 Thread Paolo Bonzini
This is required to decouple block jobs from running in an AioContext. With multiqueue block devices, a BlockDriverState does not really belong to a single AioContext. The solution is to first wait until all I/O operations are complete; then loop in the main thread for the block job to complete