From: Dan Malek <dan@embeddededge.com>
To: "David C. Chiu" <dchiu@ariodata.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Enlarging Kernel Stack (doesn't this question ever go away?)
Date: Mon, 24 Jun 2002 18:28:33 -0400 [thread overview]
Message-ID: <3D179D11.3010009@embeddededge.com> (raw)
In-Reply-To: 8A098FDFC6EED94B872CA2033711F86F0EC044@orion.ariodata.com
David C. Chiu wrote:
> Thanks for the tip, however the problem isn't that we are allocating
> large stack variables but we have deeply nested calls...
Hmmmm.....Don't do that, then :-) The stack plus thread structures
consist of two pages. I don't know how many places may still assume
that in the code. Due to both physical and virtual access to the pages,
I think they may also have to be physically contiguous (they used to be),
so you will have to allocate 4 pages as the next step.
Good Luck.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-24 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 22:11 Enlarging Kernel Stack (doesn't this question ever go away?) David C. Chiu
2002-06-24 22:28 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-24 20:50 David C. Chiu
2002-06-24 21:42 ` Tom Rini
2002-06-24 22:05 ` Dan Malek
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=3D179D11.3010009@embeddededge.com \
--to=dan@embeddededge.com \
--cc=dchiu@ariodata.com \
--cc=linuxppc-embedded@lists.linuxppc.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 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.