[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v3] xen-disk: use an IOThread per instance

From: Paul Durrant
Subject: Re: [Qemu-devel] [PATCH v3] xen-disk: use an IOThread per instance
Date: Thu, 9 Nov 2017 09:30:45 +0000

> -----Original Message-----
> From: Stefan Hajnoczi [mailto:address@hidden
> Sent: 08 November 2017 17:42
> To: Paul Durrant <address@hidden>
> Cc: address@hidden; address@hidden; Anthony
> Perard <address@hidden>; Kevin Wolf <address@hidden>;
> Stefano Stabellini <address@hidden>; Max Reitz <address@hidden>
> Subject: Re: [Qemu-devel] [PATCH v3] xen-disk: use an IOThread per
> instance
> On Tue, Nov 07, 2017 at 05:46:53AM -0500, Paul Durrant wrote:
> > This patch allocates an IOThread object for each xen_disk instance and
> > sets the AIO context appropriately on connect. This allows processing
> > of I/O to proceed in parallel.
> >
> > The patch also adds tracepoints into xen_disk to make it possible to
> > follow the state transtions of an instance in the log.
> virtio-blk and virtio-scsi allow the user to specify an IOThread object.
> This allows users to configure the device<->IOThread mapping any way
> they like (e.g. 1:1, M:N).  Are you sure you want to hard-code the
> IOThread mapping?


  Realistically it's the only option at the moment. Xen PV backends are not 
configured bu QAPI... so no ability to control them from the command line or 
QMP. This is something I seriously intend to address in the near future but, 
for now, I simply want to unlock the performance boost that IOThread can 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]