From: Nathan Froyd <froydnj@codesourcery.com>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: bigger default stack
Date: Thu, 3 Mar 2011 07:46:27 -0800 [thread overview]
Message-ID: <20110303154626.GA23686@codesourcery.com> (raw)
In-Reply-To: <20110303153737.GA23633@afflict.kos.to>
On Thu, Mar 03, 2011 at 05:37:37PM +0200, Riku Voipio wrote:
> PTHREAD_STACK_MIN (16KB) is somewhat inadequate for a new stack. follow
> the pthread_create defaults, ie setting to RLIMIT_STACK or if unlimited
> to 2MB.
For what sort oof cases is it inadequate? This stack is just for QEMU's
usage and QEMU shouldn't be using very much. The target thread could
use quite a bit of course, but that's handled elsewhere.
-Nathan
next prev parent reply other threads:[~2011-03-03 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 15:37 [Qemu-devel] [PATCH] linux-user: bigger default stack Riku Voipio
2011-03-03 15:46 ` Nathan Froyd [this message]
2011-03-03 16:01 ` Peter Maydell
2011-03-03 16:15 ` Riku Voipio
2011-03-03 16:46 ` Nathan Froyd
2011-03-04 8:15 ` Riku Voipio
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=20110303154626.GA23686@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).