linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ulrich Drepper" <drepper@gmail.com>
To: "Hugh Dickins" <hugh@veritas.com>
Cc: "Davide Libenzi" <davidel@xmailserver.org>,
	blaisorblade@yahoo.it,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2/3] MAP_NOZERO - implement sys_brk2()
Date: Wed, 27 Jun 2007 11:52:27 -0700	[thread overview]
Message-ID: <a36005b50706271152o2ba87c69h99c51a3605f977ae@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706271807330.22337@blonde.wat.veritas.com>

On 6/27/07, Hugh Dickins <hugh@veritas.com> wrote:
> The absolute virtual addresses are randomized, yes; but do a sequence
> of mmaps and they come back adjacent to each other, and so mergable.
> Or does your distro include a kernel patch to randomize them relative
> to each other?

Each individual mmap is supposed to be randomized, yes.  If this
doesn't happen in one of our kernels right now something broken.  You
wouldn't have effective ASLR if all relative address remain the same.


> It _might_ turn out to be more attractive, not to rely on that
> peculiar sys_remap_file_pages, but make all our vmas independent
> of protections, and hang differently protected ranges off them.
> Maybe.

That's what I think is done or at least should be done.

If you want to be shocked, look at some really big Java apps.
Hundreds or thousands of threads, lots of mmap allocation.  We might
have 10,000 VMAs.  Searching becomes a problem and if the protection
information be stored somewhere else and you safe the VMA data
structures there is even some memory saving possible.

I definitely thing that this is an area which warrants looking at.  We
haven't yet seen the worst of VMA usage.  The move to 64-bit is only
just beginning and wait what people think they can do with 48+ bits of
address space.

  parent reply	other threads:[~2007-06-27 18:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27  2:44 [patch 2/3] MAP_NOZERO - implement sys_brk2() Davide Libenzi
2007-06-27  3:07 ` Rik van Riel
2007-06-27  3:33   ` Davide Libenzi
2007-06-27  3:45   ` Ulrich Drepper
2007-06-27  4:11     ` Rik van Riel
2007-06-27  5:04       ` Ulrich Drepper
2007-06-27  3:48 ` Ulrich Drepper
2007-06-27  3:55   ` Davide Libenzi
2007-06-27  5:02     ` Ulrich Drepper
2007-06-27 12:32       ` Hugh Dickins
2007-06-27 15:59         ` Davide Libenzi
2007-06-27 17:01         ` Ulrich Drepper
2007-06-27 17:43           ` Hugh Dickins
2007-06-27 18:13             ` Davide Libenzi
2007-06-27 18:32               ` Hugh Dickins
2007-06-27 18:45                 ` Davide Libenzi
2007-06-27 22:11                   ` Nicholas Miell
2007-06-28  0:17                     ` Davide Libenzi
2007-06-28  2:58                       ` Davide Libenzi
2007-06-30  7:52                     ` Andrew Morton
2007-06-27 18:52             ` Ulrich Drepper [this message]
2007-06-27 19:32               ` Hugh Dickins
2007-06-27 19:00           ` Rik van Riel
2007-06-27 19:22             ` Davide Libenzi
2007-06-27 16:05       ` Davide Libenzi

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=a36005b50706271152o2ba87c69h99c51a3605f977ae@mail.gmail.com \
    --to=drepper@gmail.com \
    --cc=blaisorblade@yahoo.it \
    --cc=davidel@xmailserver.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).