From: Markus Armbruster <armbru@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com,
peter.maydell@linaro.org, mst@redhat.com, dgilbert@redhat.com,
mreitz@redhat.com, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH V2 6/6] coroutine: reduce stack size to 64kB
Date: Wed, 06 Jul 2016 10:13:27 +0200 [thread overview]
Message-ID: <87r3b7fal4.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <1467635487-9329-7-git-send-email-pl@kamp.de> (Peter Lieven's message of "Mon, 4 Jul 2016 14:31:27 +0200")
Peter Lieven <pl@kamp.de> writes:
> evaluation with the recently introduced maximum stack usage monitoring revealed
> that the actual used stack size was never above 4kB so allocating 1MB stack
> for each coroutine is a lot of wasted memory. So reduce the stack size to
> 64kB which should still give enough head room.
Suggest to mention the guard page here, to make it sound less scary.
next prev parent reply other threads:[~2016-07-06 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 12:31 [Qemu-devel] [PATCH V2 0/6] coroutine: mmap stack memory and stack size Peter Lieven
2016-07-04 12:31 ` [Qemu-devel] [PATCH V2 1/6] oslib-posix: add helpers for stack alloc and free Peter Lieven
2016-07-06 8:12 ` Markus Armbruster
2016-07-08 17:18 ` Richard Henderson
2016-07-04 12:31 ` [Qemu-devel] [PATCH V2 2/6] coroutine: add a macro for the coroutine stack size Peter Lieven
2016-07-04 12:31 ` [Qemu-devel] [PATCH V2 3/6] coroutine-ucontext: use helper for allocating stack memory Peter Lieven
2016-07-04 12:31 ` [Qemu-devel] [PATCH V2 4/6] coroutine-sigaltstack: " Peter Lieven
2016-07-04 12:31 ` [Qemu-devel] [PATCH V2 5/6] oslib-posix: add a configure switch to debug stack usage Peter Lieven
2016-07-04 12:31 ` [Qemu-devel] [PATCH V2 6/6] coroutine: reduce stack size to 64kB Peter Lieven
2016-07-06 8:13 ` Markus Armbruster [this message]
2016-07-04 14:54 ` [Qemu-devel] [PATCH V2 0/6] coroutine: mmap stack memory and stack size Paolo Bonzini
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=87r3b7fal4.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.