Kevin Wolf writes:
> Am 15.03.2019 um 16:33 hat Sergio Lopez geschrieben:
>>
>> Stefan Hajnoczi writes:
>>
>> > On Thu, Mar 14, 2019 at 06:31:34PM +0100, Sergio Lopez wrote:
>> >> Our current AIO path does a great job at unloading the work from the VM,
>> >> and combined with IOThreads provide
Am 18.03.2019 um 13:44 hat Sergio Lopez geschrieben:
> Kevin Wolf writes:
> > Am 15.03.2019 um 16:33 hat Sergio Lopez geschrieben:
> >> Stefan Hajnoczi writes:
> >> > On Thu, Mar 14, 2019 at 06:31:34PM +0100, Sergio Lopez wrote:
> >> >> Our current AIO path does a great job at unloading the work fr
Kevin Wolf writes:
> Am 15.03.2019 um 16:33 hat Sergio Lopez geschrieben:
>>
>> Stefan Hajnoczi writes:
>>
>> > On Thu, Mar 14, 2019 at 06:31:34PM +0100, Sergio Lopez wrote:
>> >> Our current AIO path does a great job at unloading the work from the VM,
>> >> and combined with IOThreads provide
Am 17.03.2019 um 06:58 hat Fam Zheng geschrieben:
> > On Mar 15, 2019, at 01:31, Sergio Lopez wrote:
> >
> > Hi,
> >
> > Our current AIO path does a great job at unloading the work from the VM,
> > and combined with IOThreads provides a good performance in most
> > scenarios. But it also comes w
> On Mar 15, 2019, at 01:31, Sergio Lopez wrote:
>
> Hi,
>
> Our current AIO path does a great job at unloading the work from the VM,
> and combined with IOThreads provides a good performance in most
> scenarios. But it also comes with its costs, in both a longer execution
> path and the need
Am 15.03.2019 um 16:33 hat Sergio Lopez geschrieben:
>
> Stefan Hajnoczi writes:
>
> > On Thu, Mar 14, 2019 at 06:31:34PM +0100, Sergio Lopez wrote:
> >> Our current AIO path does a great job at unloading the work from the VM,
> >> and combined with IOThreads provides a good performance in most
>
Stefan Hajnoczi writes:
> On Thu, Mar 14, 2019 at 06:31:34PM +0100, Sergio Lopez wrote:
>> Our current AIO path does a great job at unloading the work from the VM,
>> and combined with IOThreads provides a good performance in most
>> scenarios. But it also comes with its costs, in both a longer
On Thu, Mar 14, 2019 at 06:31:34PM +0100, Sergio Lopez wrote:
> Our current AIO path does a great job at unloading the work from the VM,
> and combined with IOThreads provides a good performance in most
> scenarios. But it also comes with its costs, in both a longer execution
> path and the need of
Hi,
Our current AIO path does a great job at unloading the work from the VM,
and combined with IOThreads provides a good performance in most
scenarios. But it also comes with its costs, in both a longer execution
path and the need of the intervention of the scheduler at various
points.
There's on