From: Arjan van de Ven <arjanv@redhat.com>
To: Utz Lehmann <lkml@de.tecosim.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@zip.com.au>
Subject: Re: [PATCH] flexmmap: optimise mmap_base gap for hard limited stack
Date: Fri, 17 Sep 2004 15:21:20 +0200 [thread overview]
Message-ID: <20040917132120.GA3151@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040917131829.GA15000@de.tecosim.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Fri, Sep 17, 2004 at 03:18:30PM +0200, Utz Lehmann wrote:
> Ulrich Drepper [drepper@redhat.com] wrote:
> > > A check for CAP_SYS_RESOURCE can be added. But i dont think it's worth.
> >
> > It is needed. Otherwise how do you allow increasing the stack size
> > again once it has been limited? I've no problem with using the smallest
> > reserved stack region with !CAP_SYS_RESOURCE, but otherwise the existing
> > method should be used.
>
> I made that change. The following patch only reduce the gap when the
> application can not extend the stack space anyway (hard limited stack &&
> !CAP_SYS_RESOURCE). All other cases stay unchanged except for the 1 MB hole
> for soft limited stacks >128 MB.
>
> It gave a nice way for making most of the default 128 MB gap usable for
> applications. Just run them with a hard stack limit.
>
> Now i can allocate more than 3.8GiB in one chunk on x86 (this patch +
> exec-shield + 4g/4g + ulimit -H -s 8192).
Ack; nice work!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-09-17 13:21 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
2004-09-16 19:07 ` Ulrich Drepper
2004-09-17 13:18 ` Utz Lehmann
2004-09-17 13:21 ` Arjan van de Ven [this message]
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=20040917132120.GA3151@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=akpm@zip.com.au \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@de.tecosim.com \
/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