From: Gerrit Huizenga <gh@us.ibm.com>
To: Andi Kleen <ak@muc.de>
Cc: akpm@digeo.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.43-mm2] New shared page table patch
Date: Wed, 23 Oct 2002 10:49:44 -0700 [thread overview]
Message-ID: <E184PdY-0005Nc-00@w-gerrit2> (raw)
In-Reply-To: Your message of 23 Oct 2002 05:03:38 +0200. <m3fzuxq2k5.fsf@averell.firstfloor.org>
In message <m3fzuxq2k5.fsf@averell.firstfloor.org>, > : Andi Kleen writes:
> Gerrit Huizenga <gh@us.ibm.com> writes:
>
> > If the shared pte patch had mmap support, then all shared libraries
> > would benefit. Might need to align them to 4 MB boundaries for best
> > results, which would also be easy for libraries with unspecified
> > attach addresses (e.g. most shared libraries).
>
> But only if the shared libraries are a multiple of 2/4MB, otherwise you'll
> waste memory. Or do you propose to link multiple mmap'ed libraries together
> into the same page ?
Hmm. I didn't propose. Sounds cool. But that would have to happen
at the compiler's loader level, not the dynamic linker side of things,
which makes it less likely. Someone once proposed a mega-library where
the big/key shared objects were linked together which would make this
somewhat more practical.
But even wasting a bit of space for a few key libraries, even if they
are smaller than 4 MB (or 2 MB) on ia32 (ia32 PAE) might be worth a
bit of TLB & general overhead (e.g. like the kernel text pages). And,
if shared, even a bigger win.
> But I agree it would be nice to have a chattr for files that tells
> mmap() to use large pages for them.
Yep - that would be ideal - like the old sticky flag on binaries.
As a patch, that would make it easy to compare performance diffs as
well. Probably good for things like Oracle or DB2 as well.
gerrit
next prev parent reply other threads:[~2002-10-23 17:44 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 23:06 [PATCH 2.5.43-mm2] New shared page table patch Dave McCracken
2002-10-19 1:32 ` Ed Tomlinson
2002-10-19 19:17 ` Bill Davidsen
2002-10-19 19:36 ` Dave McCracken
2002-10-20 4:20 ` Eric W. Biederman
2002-10-20 6:18 ` Martin J. Bligh
2002-10-21 14:55 ` Eric W. Biederman
2002-10-21 15:21 ` Martin J. Bligh
2002-10-22 3:54 ` Eric W. Biederman
2002-10-22 5:55 ` Martin J. Bligh
2002-10-22 16:09 ` Rik van Riel
2002-10-22 16:14 ` Martin J. Bligh
2002-10-22 18:06 ` Bill Davidsen
2002-10-22 19:02 ` Martin J. Bligh
2002-10-22 19:21 ` Dave McCracken
2002-10-24 10:50 ` Bill Davidsen
2002-10-24 14:22 ` Martin J. Bligh
2002-10-24 14:38 ` Dave McCracken
2002-10-24 14:51 ` Martin J. Bligh
2002-10-25 17:31 ` Bill Davidsen
2002-10-24 10:42 ` Bill Davidsen
2002-10-22 17:19 ` Benjamin LaHaise
2002-10-22 17:36 ` Martin J. Bligh
2002-10-22 17:45 ` Benjamin LaHaise
2002-10-22 17:56 ` Andrew Morton
2002-10-22 18:01 ` Benjamin LaHaise
2002-10-22 19:03 ` Martin J. Bligh
2002-10-22 20:23 ` Alan Cox
2002-10-22 21:33 ` Gerrit Huizenga
2002-10-22 18:22 ` Alan Cox
2002-10-22 18:47 ` Gerrit Huizenga
2002-10-22 18:55 ` Benjamin LaHaise
2002-10-22 19:27 ` Gerrit Huizenga
2002-10-22 19:29 ` Benjamin LaHaise
2002-10-22 19:56 ` Arjan van de Ven
2002-10-22 14:26 ` Rik van Riel
2002-10-22 17:09 ` Andrew Morton
2002-10-22 17:15 ` Rik van Riel
2002-10-22 18:36 ` Dave McCracken
2002-10-22 18:49 ` Andrew Morton
2002-10-22 19:06 ` Gerrit Huizenga
2002-10-22 19:29 ` Dave McCracken
2002-10-23 3:03 ` Andi Kleen
2002-10-23 3:10 ` Rik van Riel
2002-10-23 17:49 ` Gerrit Huizenga [this message]
[not found] ` <Pine.LNX.4.44L.0210221514430.1648-100000@duckman.distro.conecti va>
2002-10-22 19:11 ` Ulrich Drepper
2002-10-22 19:29 ` Gerrit Huizenga
2002-10-22 18:45 ` Gerrit Huizenga
2002-10-22 17:54 ` Bill Davidsen
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=E184PdY-0005Nc-00@w-gerrit2 \
--to=gh@us.ibm.com \
--cc=ak@muc.de \
--cc=akpm@digeo.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