All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <ak@muc.de>, Andrew Morton <akpm@digeo.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] mmap-speedup-2.5.42-C3
Date: Wed, 16 Oct 2002 04:22:09 -0400	[thread overview]
Message-ID: <20021016042209.D5659@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210161023530.4906-100000@localhost.localdomain>; from mingo@elte.hu on Wed, Oct 16, 2002 at 10:27:07AM +0200

On Wed, Oct 16, 2002 at 10:27:07AM +0200, Ingo Molnar wrote:
> 
> On Wed, 16 Oct 2002, Jakub Jelinek wrote:
> 
> > Libraries mapped by dynamic linker are mapped without MAP_FIXED and
> > unless you use prelinking, with 0 virtual address, ie. they all end up
> > above 1GB. And 99% of libraries uses different protections, for the
> > read-only and read-write segment.
> 
> right - only the bss (brk-allocated) ones are below 1GB it appears. I did
> a quick check on a KDE app and 3 mappings were below 1GB, and 116(!)  
> mappings were above 1GB. And even if it wasnt for the different
> protections, they use different files to map to so they have to be in
> different vmas, no matter what.
> 
> i'm wondering about prelinking though - wont that reduce the number of
> mappings radically?

It won't, the number of mappings will be exactly the same. It still needs
to mmap all the libraries and honour the protections.
But you might have holes in between the mappings if prelinking, while
you usually don't have many if not prelinking.
That's because prelink assigns a separate VA slot for each library (well,
with --conserve-memory two libraries might get the same VA slot if they
never appear together in any program).

	Jakub

  reply	other threads:[~2002-10-16  8:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 13:11 [patch] mmap-speedup-2.5.42-C3 Ingo Molnar
2002-10-15 13:11 ` Ingo Molnar
2002-10-15 18:09 ` Andrew Morton
2002-10-15 18:09   ` Andrew Morton
2002-10-15 21:30   ` Andi Kleen
2002-10-16  8:03     ` Ingo Molnar
2002-10-16  8:07       ` Jakub Jelinek
2002-10-16  8:27         ` Ingo Molnar
2002-10-16  8:22           ` Jakub Jelinek [this message]
2002-10-16  9:16         ` Andi Kleen
2002-10-16  9:47           ` Ingo Molnar
2002-10-16 12:08             ` Jakub Jelinek
2002-10-16  1:14 ` Saurabh Desai
2002-10-16  1:14   ` Saurabh Desai
2002-10-16  8:14   ` Ingo Molnar
2002-10-16  8:14     ` Ingo Molnar
2002-10-16 14:52     ` Linus Torvalds
2002-10-16 14:52       ` Linus Torvalds
2002-10-16 15:49       ` Arjan van de Ven
2002-10-16 16:10         ` Andrew Morton
2002-10-16 16:10           ` Andrew Morton

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=20021016042209.D5659@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=ak@muc.de \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@transmeta.com \
    /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.