From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Hugh Dickins <hugh@veritas.com>, 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 15:36:13 -0700 [thread overview]
Message-ID: <20070315153613.3d2eaf10.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070315233343.662b019c@lxorguk.ukuu.org.uk>
On Thu, 15 Mar 2007 23:33:43 +0000
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > Stack RSS should certainly be included in Committed_AS,
> > but RLIMIT_STACK merely limits how big the stack vma may grow to:
> > at any moment the stack vma is probably very much smaller,
> > and only its current size is accounted in Committed_AS.
>
> With a typical size as a fuzz factor preaccounted in later kernels.
Where's that done?
> > > > Is this the intended behaviour?
> > >
> > > That sounds like a bug to me.
> >
> > I'm suspecting it's an oddity rather than a bug.
>
> It is intended behaviour.
Each instance of
main()
{
sleep(100);
}
appears to increase Committed_AS by around 200kb. But we've committed to
providing it with 8MB for stack.
How come this is correct?
next prev parent reply other threads:[~2007-03-15 22:36 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
2007-03-15 23:33 ` Alan Cox
2007-03-15 22:36 ` Andrew Morton [this message]
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=20070315153613.3d2eaf10.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.