From: Bill Davidsen <davidsen@tmr.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Dave McCracken <dmccr@us.ibm.com>, Andrew Morton <akpm@digeo.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [PATCH 2.5.43-mm2] New shared page table patch
Date: Thu, 24 Oct 2002 06:42:44 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1021024063555.14473A-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <407130000.1035313347@flay>
On Tue, 22 Oct 2002, Martin J. Bligh wrote:
> > I'm just trying to decide what this might do for a news server with
> > hundreds of readers mmap()ing a GB history file. Benchmarks show the 2.5
> > has more latency the 2.4, and this is likely to make that more obvious.
> >
> > Is there any way to to have this only on processes which really need it?
> > define that any way you wish, including hanging a capability on the
> > executable to get spt.
>
> Uh, what are you referring to here? Large pages or shared pagetables?
> You can't mmap filebacked stuff with larged pages (nixed by Linus).
Shared pagetables, it's a non-root application.
> And yes, large pages have to be specified explicitly by the app.
> On the other hand, I don't think shared pagetables have an mmap hook,
That could be interesting... so if the server has a mmap()ed file and
forks a child when a connection comes in, the tables would get duplicated
even with the patch? That's not going to help me.
> though that'd be easy enough to add. And if you're not reading the whole
> history file, presumably the PTEs will only be sparsely instantiated anyway.
I have to go back and look at that code to be sure, you may be right.
There certainly are other things which are mmap()ed by all children (or
threads, depending on implementation) which might benefit since they're
moderately large and do have hundreds to thousands of copies.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-10-24 10:42 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 23:06 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 [this message]
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-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=Pine.LNX.3.96.1021024063555.14473A-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@digeo.com \
--cc=dmccr@us.ibm.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=riel@conectiva.com.br \
/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