On 11/04/2016 07:10 AM, Fam Zheng wrote:
>> Do we even need a IOThreadGroup object ? Can't we just explicitly pass
>> a list of IOThread object IDs to the device. eg something like
>>
>>-device virtio-blk-pci,iothread=t1,iothread=t2,iothread=t3
>
> Is that a supported syntax by qdev/QOM?
Wit
On Fri, 11/04 11:03, Daniel P. Berrange wrote:
> On Fri, Nov 04, 2016 at 10:58:04AM +, Stefan Hajnoczi wrote:
> > On Wed, Oct 19, 2016 at 04:04:50PM +0800, Fam Zheng wrote:
> > > The option specifies how many threads to spawn under the iothread
> > > object. All threads share the same AioContex
On Fri, Nov 04, 2016 at 10:58:04AM +, Stefan Hajnoczi wrote:
> On Wed, Oct 19, 2016 at 04:04:50PM +0800, Fam Zheng wrote:
> > The option specifies how many threads to spawn under the iothread
> > object. All threads share the same AioContext so they can safely run
> > (contend) together.
> >
>
On Wed, Oct 19, 2016 at 04:04:50PM +0800, Fam Zheng wrote:
> The option specifies how many threads to spawn under the iothread
> object. All threads share the same AioContext so they can safely run
> (contend) together.
>
> With AioContext going away, the spawns will natually enable the block
> mu
The option specifies how many threads to spawn under the iothread
object. All threads share the same AioContext so they can safely run
(contend) together.
With AioContext going away, the spawns will natually enable the block
multi-queue work.
Signed-off-by: Fam Zheng
---
Based on v2 of Paolo's
