All of lore.kernel.org
 help / color / mirror / Atom feed
From: Utz Lehmann <lkml@de.tecosim.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Utz Lehmann <lkml@de.tecosim.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] flexmmap: optimise mmap_base gap for hard limited stack
Date: Thu, 16 Sep 2004 20:21:39 +0200	[thread overview]
Message-ID: <20040916182139.GA21870@de.tecosim.com> (raw)
In-Reply-To: <20040916174529.GA16439@devserv.devel.redhat.com>

Arjan van de Ven [arjanv@redhat.com] wrote:
> On Thu, Sep 16, 2004 at 06:56:13PM +0200, Utz Lehmann wrote:
> > Hi
> > 
> > With the flexmmap memory layout there is at least a 128 MB gap between
> > mmap_base and TASK_SIZE. I think this is for the case that a running process
> > can expand it's stack soft rlimit.
> > 
> > If there is a hard limit for the stack this minium gap is just a waste of
> > space. This patch reduce the gap to the hard limit + 1 MB hole. If a process
> > has a 8192 KB hard limit it have additional 119 MB space available over the
> > current behavior.
> 
> 
> I'm not so convinced this is the right approach... a bit of room for the
> apps to increase their stack sounds useful. (and a "reasonable" amount is
> SuS specified afaik, 128Mb is quite reasonable)

This is only for a hard limited (rlim_max) stack. A non-root application
can not increase it anyway.
The default (rlim_cur = ~8MB, rlim_max = ulimited) is unchanged and get a
gap of 128MB.

A check for CAP_SYS_RESOURCE can be added. But i dont think it's worth.

  reply	other threads:[~2004-09-16 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 16:56 [PATCH] flexmmap: optimise mmap_base gap for hard limited stack Utz Lehmann
2004-09-16 17:38 ` Andrea Arcangeli
2004-09-17 13:24   ` Utz Lehmann
2004-09-16 17:45 ` Arjan van de Ven
2004-09-16 18:21   ` Utz Lehmann [this message]
2004-09-16 19:07     ` Ulrich Drepper
2004-09-17 13:18       ` Utz Lehmann
2004-09-17 13:21         ` Arjan van de Ven

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=20040916182139.GA21870@de.tecosim.com \
    --to=lkml@de.tecosim.com \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@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.