From: Jeff Dike <jdike@addtoit.com>
To: Rob Landley <rob@landley.net>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Do we care about 4k stacks?
Date: Mon, 21 Nov 2005 09:56:00 -0500 [thread overview]
Message-ID: <20051121145600.GA27086@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200511210019.36848.rob@landley.net>
On Mon, Nov 21, 2005 at 12:19:36AM -0600, Rob Landley wrote:
> Just curious if this is at all relevant to us, in light of the "yank 8k
> stacks" patch proposed...
That's just on i386. Each arch defines its own stack size, and UML uses
16K. Not that that's good, so we might be following i386 at some point, at
least to 8K.
> $ make checkstack
> objdump -d vmlinux $(find . -name '*.ko') | \
> perl /home/landley/linux-2.6.15-rc1/scripts/checkstack.pl i386
> 0xa010ddcf buffered_vfprintf: 33168
> 0xa010deca buffered_vfprintf: 33168
> 0xa00e5d5b buffered_vfprintf: 8416
> 0xa00e5e43 buffered_vfprintf: 8416
I don't think these are of concern, but feel free to double-check :-)
If you look at the code, you'll see some care in making sure that certain
things (like printf) run only on the initial process stack, which is expanded
as needed by the host, and not on a UML kernel, which isn't.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-11-21 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 6:19 [uml-devel] Do we care about 4k stacks? Rob Landley
2005-11-21 14:56 ` Jeff Dike [this message]
2005-11-22 19:24 ` Blaisorblade
2005-11-23 4:44 ` Rob Landley
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=20051121145600.GA27086@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.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.