All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Eric Blake <eblake@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow2: allocate cluster_cache/cluster_data on demand
Date: Sat, 19 Aug 2017 18:50:03 +1000	[thread overview]
Message-ID: <3620ddfa-5e8a-0730-7218-32d351d6e1e5@ozlabs.ru> (raw)
In-Reply-To: <8cb05e90-d7f0-6448-b6ff-68a75ebb67d0@ozlabs.ru>

[-- Attachment #1: Type: text/plain, Size: 2249 bytes --]

On 19/08/17 12:53, Alexey Kardashevskiy wrote:
> On 19/08/17 12:46, Alexey Kardashevskiy wrote:
>> On 19/08/17 01:18, Eric Blake wrote:
>>> On 08/18/2017 08:31 AM, Stefan Hajnoczi wrote:
>>>> Most qcow2 files are uncompressed so it is wasteful to allocate (32 + 1)
>>>> * cluster_size + 512 bytes upfront.  Allocate s->cluster_cache and
>>>> s->cluster_data when the first read operation is performance on a
>>>> compressed cluster.
>>>>
>>>> The buffers are freed in .bdrv_close().  .bdrv_open() no longer has any
>>>> code paths that can allocate these buffers, so remove the free functions
>>>> in the error code path.
>>>>
>>>> Reported-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>>>> Cc: Kevin Wolf <kwolf@redhat.com>
>>>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>>>> ---
>>>> Alexey: Does this improve your memory profiling results?
>>>
>>> Is this a regression from earlier versions? 
>>
>> Hm, I have not thought about this.
>>
>> So. I did bisect and this started happening from
>> 9a4c0e220d8a4f82b5665d0ee95ef94d8e1509d5
>> "hw/virtio-pci: fix virtio behaviour"
>>
>> Before that, the very same command line would take less than 1GB of
>> resident memory. That thing basically enforces virtio-1.0 for QEMU <=2.6
>> which means that upstream with "-machine pseries-2.6" works fine (less than
>> 1GB), "-machine pseries-2.7" does not (close to 7GB, sometime even 9GB).
>>
>> Then I tried bisecting again, with
>> "scsi=off,disable-modern=off,disable-legacy=on" on my 150 virtio-block
>> devices, started from
>> e266d421490e0 "virtio-pci: add flags to enable/disable legacy/modern" (it
>> added the disable-modern switch) which uses 2GB of memory.
>>
>> I ended up with ada434cd0b44 "virtio-pci: implement cfg capability".
>>
>> Then I removed proxy->modern_as on v2.10.0-rc3 (see below) and got 1.5GB of
>> used memory (yay!)
>>
>> I do not really know how to reinterpret all of this, do you?
>>
>>
>> Note: 1GB..9GB numbers from below are the peak values from valgrind's
> 
> s/from below/from above/ , sorry, bad cut-n-paste :)


Just realized - I should have replied with this to "Memory use with >100
virtio devices" actually, sorry for the confusion.


-- 
Alexey


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 839 bytes --]

  reply	other threads:[~2017-08-19  8:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 13:31 [Qemu-devel] [PATCH] qcow2: allocate cluster_cache/cluster_data on demand Stefan Hajnoczi
2017-08-18 15:18 ` Eric Blake
2017-08-19  2:46   ` Alexey Kardashevskiy
2017-08-19  2:53     ` Alexey Kardashevskiy
2017-08-19  8:50       ` Alexey Kardashevskiy [this message]
2017-08-22  4:56     ` Alexey Kardashevskiy
2017-08-30 17:20       ` Stefan Hajnoczi
2017-08-31  0:03         ` Alexey Kardashevskiy
2017-08-21 13:50   ` Stefan Hajnoczi
2017-08-19  1:01 ` Alexey Kardashevskiy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3620ddfa-5e8a-0730-7218-32d351d6e1e5@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.