From: Ralf Baechle <ralf@linux-mips.org>
To: ?? <kevin@gv.com.tw>
Cc: linux-mips@linux-mips.org
Subject: Re: enlarge KERNEL_STACK_SIZE
Date: Tue, 10 Dec 2002 13:35:36 +0100 [thread overview]
Message-ID: <20021210133536.A17306@linux-mips.org> (raw)
In-Reply-To: <00da01c2a047$2aa9f9e0$e20310ac@gv.com.tw>; from kevin@gv.com.tw on Tue, Dec 10, 2002 at 08:25:03PM +0800
On Tue, Dec 10, 2002 at 08:25:03PM +0800, ?? wrote:
> how to enlarge KERNEL_STACK_SIZE?
>
> is it enough if i only change
> the definition of KERNEL_STACK_SIZE in include/asm-mips/processor.h ?
No, other changes would be needed also. HOWEVER: It's a very bad idea.
Stacks larger than 8kB require allocation of order 2 or even bigger
pages which will make the kernel unreliable. I really recommend to stick
with the current 8kB stacks.
Ralf
next prev parent reply other threads:[~2002-12-10 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 11:50 sgi linux version 2.4.18 cvs ??
2002-12-05 11:50 ` ??
2002-12-05 12:23 ` Ralf Baechle
2002-12-10 12:25 ` enlarge KERNEL_STACK_SIZE ??
2002-12-10 12:25 ` ??
2002-12-10 12:35 ` Ralf Baechle [this message]
2002-12-20 3:37 ` [help] exec_usermodehelper() then content of CURRENT is destroyed ??
2002-12-20 3:37 ` ??
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=20021210133536.A17306@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kevin@gv.com.tw \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox