From: Martin Hicks <mort@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] 2.5 - Another user stack size patch
Date: Fri, 23 May 2003 18:34:31 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723706008@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723706006@msgid-missing>
On Fri, May 23, 2003 at 02:22:56PM -0400, DESAI,RAJESH (HP-Cupertino,ex1) wrote:
> So, what kind of apps need 1 TB stacks?
People from within SGI are claiming that some of their apps require 2GB
of stack per processor, so even with existing systems we're looking at
128GB of stack space. I imagine that the high-end SSI NUMA clusters
will get even bigger in the next while. The 1TB number was just a nice
round number.
mh
--
Wild Open Source Inc. mort@wildopensource.com
next prev parent reply other threads:[~2003-05-23 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 18:15 [Linux-ia64] [PATCH] 2.5 - Another user stack size patch Martin Hicks
2003-05-23 18:22 ` DESAI,RAJESH (HP-Cupertino,ex1)
2003-05-23 18:34 ` Martin Hicks [this message]
2003-05-23 18:37 ` DESAI,RAJESH (HP-Cupertino,ex1)
2003-05-23 19:04 ` Martin Hicks
2003-05-23 19:28 ` Martin Hicks
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-105590723706008@msgid-missing \
--to=mort@wildopensource.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