From: Martin Hicks <mort@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: [PATCH] Increase size of user stack
Date: Mon, 12 May 2003 14:59:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705730@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705638@msgid-missing>
On Mon, May 12, 2003 at 03:44:17PM +0100, Matthew Wilcox wrote:
> On Mon, May 12, 2003 at 10:38:44AM -0400, Martin Hicks wrote:
> > >
> > (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?
Maybe I'm missing something, but what happens if a process is created
using the default 2GB between the RBS and the stack and sometime
later the process does a setrlimit to 100GB of stack. How do the
stack and RBS get moved around to make enough room between the two
start addresses?
mh
--
Wild Open Source Inc. mort@wildopensource.com
next prev parent reply other threads:[~2003-05-12 14:59 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
2003-05-12 14:59 ` Martin Hicks [this message]
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-105590723705730@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 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.