From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: [PATCH] Increase size of user stack
Date: Mon, 05 May 2003 18:25:33 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705638@msgid-missing> (raw)
>>>>> On Mon, 5 May 2003 14:18:52 -0400, Martin Hicks <mort@wildopensource.com> said:
Martin> The current user stack size limit of 2GB is not big enough
Martin> for large SMP or SSI clusters. The following patch
Martin> increases this size from 2GB to 512GB. The new size is
Martin> negotiable, but right now SGI has programs that require over
Martin> 100GB of stack size on a 64 processor machine. Setting the
Martin> user stack size to 512GB seems like a reasonable thing to do
Martin> for future growth.
Martin> Comments?
Why not make it configurable via setrlimit() and be done with it once
and for all?
--david
next reply other threads:[~2003-05-05 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 18:25 David Mosberger [this message]
2003-05-12 14:38 ` [Linux-ia64] Re: [PATCH] Increase size of user stack Martin Hicks
2003-05-12 14:44 ` Matthew Wilcox
2003-05-12 14:59 ` Martin Hicks
2003-05-12 15:03 ` Matthew Wilcox
2003-05-12 15:36 ` Andreas Schwab
2003-05-12 19:10 ` David Mosberger
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=marc-linux-ia64-105590723705638@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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