public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: [PATCH] Increase size of user stack
Date: Mon, 12 May 2003 14:44:17 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705729@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705638@msgid-missing>

On Mon, May 12, 2003 at 10:38:44AM -0400, Martin Hicks wrote:
> On Mon, May 05, 2003 at 11:25:33AM -0700, David Mosberger wrote:
> >   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.
> > 
> > Why not make it configurable via setrlimit() and be done with it once
> > and for all?
> 
> (sorry for taking so long to respond about this)
> 
> The user stack size is configurable through setrlimit().  The default 
> size of the user stack is 8MB and the max is ~0UL.  The problem is
> the addreses that are chosen for the stack (which grows down) and the
> register backing store (which grows up) are only 2GB apart.  My patch
> simply makes this space 512GB so that large stack are possible, without
> the stack smashing into the RBS.

Yes, but why not choose the addresses based on the current setting of
current->rlim[RLIMIT_STACK].rlim_max?  We could default that setting to
2GB (ie the same as what people are using now) and then set the RBS and
the user stack min(1TB, current->rlim[RLIMIT_STACK].rlim_max) apart.
Are there any disadvantages to doing this?

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk


  parent reply	other threads:[~2003-05-12 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 18:25 [Linux-ia64] Re: [PATCH] Increase size of user stack David Mosberger
2003-05-12 14:38 ` Martin Hicks
2003-05-12 14:44 ` Matthew Wilcox [this message]
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-105590723705729@msgid-missing \
    --to=willy@debian.org \
    --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