From: William Lee Irwin III <wli@holomorphy.com>
To: Balbir Singh <balbir_soni@hotmail.com>
Cc: tigran@veritas.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] larger kernel stack (8k->16k) per task (fwd)
Date: Fri, 8 Feb 2002 13:11:51 -0800 [thread overview]
Message-ID: <20020208211151.GD767@holomorphy.com> (raw)
In-Reply-To: <F39q2pNdXfH4Ryzp5fO0000a02b@hotmail.com>
In-Reply-To: <F39q2pNdXfH4Ryzp5fO0000a02b@hotmail.com>
On Fri, Feb 08, 2002 at 12:42:02PM -0800, Balbir Singh wrote:
> It is highly recommended to use the existing stack size of
> 8KB, increasing the stack size to 16KB with an 200
> processes running on an average causes 1.5MB of
> extra memory to be used.
This sounds small compared to the costs of struct page.
Of course, I would be concerned regardless if this patch
were for anything but debugging.
Excellent work!
Cheers,
Bill
next prev parent reply other threads:[~2002-02-08 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 20:42 [patch] larger kernel stack (8k->16k) per task (fwd) Balbir Singh
2002-02-08 21:11 ` William Lee Irwin III [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-08 19:23 Balbir Singh
2002-02-08 18:40 Balbir Singh
2002-02-08 19:01 ` Tigran Aivazian
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=20020208211151.GD767@holomorphy.com \
--to=wli@holomorphy.com \
--cc=balbir_soni@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
/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.