From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
akpm@osdl.org, torvalds@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] overcommit symbolic constants
Date: Thu, 30 Sep 2004 22:26:55 +0200 [thread overview]
Message-ID: <20040930202653.GA5532@apps.cwi.nl> (raw)
In-Reply-To: <1096550863.19487.13.camel@localhost.localdomain>
On Thu, Sep 30, 2004 at 02:27:44PM +0100, Alan Cox wrote:
> What might work (if you've not already tried it) is to make the initial
> stack something like 1 or 4Mbytes. Don't map the pages but install a vma
> of that size. That would pre-reserve address space and perhaps avoid
> this. I guess if that works then make it a /proc/sys tunable for
> guaranteed stack.
A good and simple idea.
Yes, works entirely satisfactorily in my first few tests.
Andries
next prev parent reply other threads:[~2004-09-30 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 13:41 [PATCH] overcommit symbolic constants Andries.Brouwer
2004-09-30 12:53 ` Alan Cox
2004-09-30 14:19 ` Andries Brouwer
2004-09-30 13:27 ` Alan Cox
2004-09-30 20:26 ` Andries Brouwer [this message]
2004-09-30 14:25 ` Hugh Dickins
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=20040930202653.GA5532@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.