From: Chris Wright <chrisw@osdl.org>
To: Chris Bookholt <cgbookho@ncsu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: legacy_va_layout
Date: Mon, 17 Jan 2005 17:25:03 -0800 [thread overview]
Message-ID: <20050117172503.E469@build.pdx.osdl.net> (raw)
In-Reply-To: <41EC5B3A.4000004@ncsu.edu>; from cgbookho@ncsu.edu on Mon, Jan 17, 2005 at 07:41:30PM -0500
* Chris Bookholt (cgbookho@ncsu.edu) wrote:
> Could anyone explain or refer me to some documentation that explains the
> purpose of the legacy_va_layout sysctl option?
>
> Essentially, I'm looking to understand how the legacy layout is
> different from the current 2.6-series VA space layout.
The legacy mode splits a tasks vm into an area for heap, mmaps, and stack
at fixed points. Notably, mmap space started at 0x40000000, and new
mappings were searched from there scanning upward. While stack grew
down into that area and heap grew up into that area.
The non-legacy (flexmmap) approach, starts looking for mmap space just
below the largest possible (rlimit) stack size and scans downward. This
gives the most possible space to either brk or mmap heavy applications,
since the space doesn't start off as fragmented.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2005-01-18 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 0:41 legacy_va_layout Chris Bookholt
2005-01-18 1:25 ` Chris Wright [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=20050117172503.E469@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=cgbookho@ncsu.edu \
--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).