From: wind@cocodriloo.com
To: Rik van Riel <riel@surriel.com>
Cc: linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: 2.4 vm, program load, page faulting, ...
Date: Mon, 17 Mar 2003 17:52:23 +0100 [thread overview]
Message-ID: <20030317165223.GA11526@wind.cocodriloo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303171100300.2571-100000@chimarrao.boston.redhat.com>
On Mon, Mar 17, 2003 at 11:01:31AM -0500, Rik van Riel wrote:
> On Mon, 17 Mar 2003, William Lee Irwin III wrote:
> > On Sat, 15 Mar 2003, Paul Albrecht wrote:
> > >> ... Why does the kernel page fault on text pages, present in the page
> > >> cache, when a program starts? Couldn't the pte's for text present in the
> > >> page cache be resolved when they're mapped to memory?
> >
> > SVR4 did and saw an improvement wrt. page fault rate, according to
> > Vahalia.
>
> An improvement in the _page fault rate_, well DUH.
>
> > I'd like to see whether this is useful for Linux.
>
> The question is, does it result in an improvement in the
> run speed of processes...
>
> cheers,
>
> Rik
You should ask Andrew about his patch to do exactly that: he
forced all PROC_EXEC mmaps to be nonlinear-mapped and this
forced all programs to suck entire binaries into memory...
I recall he saw at least 25% improvement at launching gnome.
Andrew?
--
Antonio Vargas
next prev parent reply other threads:[~2003-03-17 16:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 4:59 2.4 vm, program load, page faulting, Paul Albrecht
2003-03-17 15:02 ` Rik van Riel
2003-03-17 15:10 ` William Lee Irwin III
2003-03-17 16:01 ` Rik van Riel
2003-03-17 16:52 ` wind [this message]
2003-03-17 16:50 ` Alex Tomas
2003-03-17 17:12 ` wind-lkml
2003-03-17 17:38 ` wind-lkml
2003-03-17 18:57 ` Marc-Christian Petersen
2003-03-17 19:06 ` wind-lkml
2003-03-17 19:34 ` wind
2003-03-17 22:05 ` Andrew Morton
2003-03-17 23:08 ` wind
2003-03-17 23:28 ` Andrew Morton
2003-03-18 0:12 ` wind
2003-03-17 16:37 ` Alex Tomas
2003-03-18 7:43 ` Paul Albrecht
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=20030317165223.GA11526@wind.cocodriloo.com \
--to=wind@cocodriloo.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@surriel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox