From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Lieven <pl@kamp.de>, Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Qemu and heavily increased RSS usage
Date: Fri, 24 Jun 2016 10:37:24 +0100 [thread overview]
Message-ID: <20160624093724.GC9558@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAFEAcA-b6M8PjzO86K6tN4qtnkv557oBjGuVBNO=cCM9Sjd8tQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
On Wed, Jun 22, 2016 at 09:56:06PM +0100, Peter Maydell wrote:
> On 22 June 2016 at 20:55, Peter Lieven <pl@kamp.de> wrote:
> > What makes the coroutine pool memory intensive is the stack size of 1MB per
> > coroutine. Is it really necessary to have such a big stack?
>
> That reminds me that I was wondering if we should allocate
> our coroutine stacks with MAP_GROWSDOWN (though if we're
> not actually using 1MB of stack then it's only going to
> be eating virtual memory, not necessarily real memory.)
Yes, MAP_GROWSDOWN will not reduce RSS.
It's possible that we can reduce RSS usage of the coroutine pool but it
will require someone to profile the pool usage patterns.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-24 9:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 8:21 [Qemu-devel] Qemu and heavily increased RSS usage Peter Lieven
2016-06-21 13:18 ` Dr. David Alan Gilbert
2016-06-21 15:12 ` Peter Lieven
2016-06-22 10:56 ` Stefan Hajnoczi
2016-06-22 19:55 ` Peter Lieven
2016-06-22 20:56 ` Peter Maydell
2016-06-24 9:37 ` Stefan Hajnoczi [this message]
2016-06-24 9:53 ` Peter Lieven
2016-06-24 9:57 ` Dr. David Alan Gilbert
2016-06-24 9:58 ` Peter Maydell
2016-06-24 10:45 ` Peter Lieven
2016-06-27 12:39 ` Stefan Hajnoczi
2016-06-27 13:33 ` Peter Lieven
2016-06-23 9:57 ` Peter Lieven
2016-06-24 22:57 ` Michael S. Tsirkin
2016-06-23 14:58 ` Peter Lieven
2016-06-23 15:00 ` Dr. David Alan Gilbert
2016-06-23 15:02 ` Peter Lieven
2016-06-23 15:21 ` Paolo Bonzini
2016-06-23 15:31 ` Peter Lieven
2016-06-23 15:47 ` Paolo Bonzini
2016-06-23 16:19 ` Peter Lieven
2016-06-23 16:53 ` Paolo Bonzini
2016-06-23 21:28 ` Peter Lieven
2016-06-24 4:10 ` Paolo Bonzini
2016-06-24 8:11 ` Peter Lieven
2016-06-24 8:20 ` Paolo Bonzini
2016-06-24 8:45 ` Peter Lieven
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=20160624093724.GC9558@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).