* RE: Enlarging Kernel Stack (doesn't this question ever go away?)
@ 2002-06-24 22:11 David C. Chiu
2002-06-24 22:28 ` Dan Malek
0 siblings, 1 reply; 5+ messages in thread
From: David C. Chiu @ 2002-06-24 22:11 UTC (permalink / raw)
To: linuxppc-embedded
Thanks for the tip, however the problem isn't that we are allocating
large stack variables but we have deeply nested calls...
-----Original Message-----
From: Dan Malek [mailto:dan@embeddededge.com]
Sent: Monday, June 24, 2002 3:06 PM
To: Tom Rini
Cc: David C. Chiu; linuxppc-embedded@lists.linuxppc.org
Subject: Re: Enlarging Kernel Stack (doesn't this question ever go
away?)
Tom Rini wrote:
> Why are you trying to enlarge the stack? This question never goes
away
> since it's almost always wrong to enlarge the stack...
That's correct......you should be allocating space with vmalloc() and
just hanging on to a pointer that you vfree() later.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Enlarging Kernel Stack (doesn't this question ever go away?)
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
0 siblings, 0 replies; 5+ messages in thread
From: Dan Malek @ 2002-06-24 22:28 UTC (permalink / raw)
To: David C. Chiu; +Cc: linuxppc-embedded
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/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Enlarging Kernel Stack (doesn't this question ever go away?)
@ 2002-06-24 20:50 David C. Chiu
2002-06-24 21:42 ` Tom Rini
0 siblings, 1 reply; 5+ messages in thread
From: David C. Chiu @ 2002-06-24 20:50 UTC (permalink / raw)
To: linuxppc-embedded
What other thing needs to be done in addition to modifying
INIT_TASK_SIZE in include/linux/sched.h? This is for the 405GP kernel.
TIA.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2002-06-24 22:28 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
-- 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
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).