From: "Ulrich Drepper" <drepper@gmail.com>
To: "Hugh Dickins" <hugh@veritas.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Dan Aloni" <da-x@monatomic.org>,
linux-kernel@vger.kernel.org
Subject: Re: thread stacks and strict vm overcommit accounting
Date: Thu, 15 Mar 2007 12:59:09 -0800 [thread overview]
Message-ID: <a36005b50703151359r3aa951dbtfedda605c0966ff1@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703152021130.21129@blonde.wat.veritas.com>
On 3/15/07, Hugh Dickins <hugh@veritas.com> wrote:
> I'm guessing that the pthread stacks are mmap'ed as greatest extents
> (probably because that's the easiest way to keep them apart), rather
> than as small MAP_GROWSDOWN areas to be expanded later on fault.
Please all, forget about MAP_GROWSDOWN. It's useless. If thread
stacks are not completely mapped (address space allocation, memory
allocation is not needed) it means subsequent unrelated mmaps can fall
into the address space which is meant to be used for the stack, hence
preventing the stack from growing.
libpthread uses an mmap for the complete stack size all the time and
this of course is accounted for in the kernel.
next prev parent reply other threads:[~2007-03-15 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 16:33 thread stacks and strict vm overcommit accounting Dan Aloni
2007-03-15 19:06 ` Andrew Morton
2007-03-15 20:37 ` Hugh Dickins
2007-03-15 20:59 ` Ulrich Drepper [this message]
2007-03-15 23:33 ` Alan Cox
2007-03-15 22:36 ` Andrew Morton
2007-03-15 23:08 ` Hugh Dickins
2007-03-16 1:31 ` Alan Cox
2007-03-16 14:43 ` Jakub Jelinek
2007-03-15 23:42 ` Dan Aloni
2007-03-16 4:29 ` KAMEZAWA Hiroyuki
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=a36005b50703151359r3aa951dbtfedda605c0966ff1@mail.gmail.com \
--to=drepper@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=da-x@monatomic.org \
--cc=hugh@veritas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).