On 24/08/2017 14:30, David Gibson wrote:
>>
>> Ideas what to tweak or what valgrind tool to try?
> valgrind probably isn't that useful at this point. I think we need to
> instrument bits of the code to find what the O(n^2) algo is and fix it.
>
> Seems to me checking if the address_spaces list is
On Thu, Aug 24, 2017 at 07:48:57PM +1000, Alexey Kardashevskiy wrote:
> On 21/08/17 15:50, Alexey Kardashevskiy wrote:
> > On 21/08/17 14:31, David Gibson wrote:
> >> On Fri, Aug 18, 2017 at 02:18:53PM +0100, Stefan Hajnoczi wrote:
> >>> On Fri, Aug 18, 2017 at 03:39:20PM +1000, Alexey Kardashevski
On 21/08/17 15:50, Alexey Kardashevskiy wrote:
> On 21/08/17 14:31, David Gibson wrote:
>> On Fri, Aug 18, 2017 at 02:18:53PM +0100, Stefan Hajnoczi wrote:
>>> On Fri, Aug 18, 2017 at 03:39:20PM +1000, Alexey Kardashevskiy wrote:
==94451== 4 of 10
On 21/08/17 14:31, David Gibson wrote:
> On Fri, Aug 18, 2017 at 02:18:53PM +0100, Stefan Hajnoczi wrote:
>> On Fri, Aug 18, 2017 at 03:39:20PM +1000, Alexey Kardashevskiy wrote:
>>> ==94451== 4 of 10
>>> ==94451== max-live:314,649,600 in 150 blocks
>>>
On Fri, Aug 18, 2017 at 02:18:53PM +0100, Stefan Hajnoczi wrote:
> On Fri, Aug 18, 2017 at 03:39:20PM +1000, Alexey Kardashevskiy wrote:
> > ==94451== 4 of 10
> > ==94451== max-live:314,649,600 in 150 blocks
> > ==94451== tot-alloc: 314,649,600 in 150
On Fri, Aug 18, 2017 at 03:39:20PM +1000, Alexey Kardashevskiy wrote:
> ==94451== 4 of 10
> ==94451== max-live:314,649,600 in 150 blocks
> ==94451== tot-alloc: 314,649,600 in 150 blocks (avg size 2097664.00)
> ==94451== deaths: none (none of thes
Hi!
We have received a report that qemu cannot handle hundreds of virtio
devices and crashes. I tried qemu with 150 virtio-block devices, 1 CPU and
and 2GB RAM (the exact command line is at the end) and found that it took
more than 5.5GB resident and 9GB virtual memory. Bit weird, I tried
valgrind
