On Fri, Dec 07, 2012 at 07:04:39PM +0100, Kevin Wolf wrote:
> Am 05.12.2012 21:47, schrieb Stefan Hajnoczi:
> > virtio-blk-data-plane is a subset implementation of virtio-blk. It only
> > handles read, write, and flush requests. It does this using a dedicated
> > thread that executes an epoll(2)-
Am 05.12.2012 21:47, schrieb Stefan Hajnoczi:
> virtio-blk-data-plane is a subset implementation of virtio-blk. It only
> handles read, write, and flush requests. It does this using a dedicated
> thread that executes an epoll(2)-based event loop and processes I/O
> using Linux AIO.
>
> This appr
Il 07/12/2012 07:06, Stefan Hajnoczi ha scritto:
> BTW I should go into slightly more detail about why I stopped short of
> implementing the notify+join approach.
>
> notify+join means stopping the event loop and data plane thread so
> that the caller is sure that virtio-blk-data-plane is quiesced
On Thu, Dec 06, 2012 at 08:35:55AM +0100, Paolo Bonzini wrote:
> Il 05/12/2012 21:47, Stefan Hajnoczi ha scritto:
> > +
> > +/* Block until pending requests have completed
> > + *
> > + * The vring continues to be serviced so ensure no new requests will be
> > added
> > + * to avoid races.
> > + *
On Thu, Dec 06, 2012 at 08:35:55AM +0100, Paolo Bonzini wrote:
> Il 05/12/2012 21:47, Stefan Hajnoczi ha scritto:
> > +
> > +/* Block until pending requests have completed
> > + *
> > + * The vring continues to be serviced so ensure no new requests will be
> > added
> > + * to avoid races.
> > + *
On Thu, Dec 06, 2012 at 01:33:58PM +0200, Michael S. Tsirkin wrote:
> On Wed, Dec 05, 2012 at 09:47:09PM +0100, Stefan Hajnoczi wrote:
> > virtio-blk-data-plane is a subset implementation of virtio-blk.
>
> I already asked this:
>
> what confuses me a bit is how, being a subset, it exposes the
>
On Wed, Dec 05, 2012 at 09:47:09PM +0100, Stefan Hajnoczi wrote:
> virtio-blk-data-plane is a subset implementation of virtio-blk.
I already asked this:
what confuses me a bit is how, being a subset, it exposes the
same feature bits. For example wce config is ineffective, right?
So I think it sho
Il 05/12/2012 21:47, Stefan Hajnoczi ha scritto:
> +
> +/* Block until pending requests have completed
> + *
> + * The vring continues to be serviced so ensure no new requests will be added
> + * to avoid races.
> + */
> +void virtio_blk_data_plane_drain(VirtIOBlockDataPlane *s)
> +{
> +qemu_mu
virtio-blk-data-plane is a subset implementation of virtio-blk. It only
handles read, write, and flush requests. It does this using a dedicated
thread that executes an epoll(2)-based event loop and processes I/O
using Linux AIO.
This approach performs very well but can be used for raw image file
