From: William Lee Irwin III <wli@holomorphy.com>
To: Rik van Riel <riel@surriel.com>
Cc: Paul Albrecht <palbrecht@uswest.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.4 vm, program load, page faulting, ...
Date: Mon, 17 Mar 2003 07:10:04 -0800 [thread overview]
Message-ID: <20030317151004.GR20188@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303171001030.2571-100000@chimarrao.boston.redhat.com>
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?
On Mon, Mar 17, 2003 at 10:02:21AM -0500, Rik van Riel wrote:
> The mmap() syscall only sets up the VMA info, it doesn't
> fill in the page tables. That only happens when the process
> page faults.
> Note that filling in a bunch of page table entries mapping
> already present pagecache pages at exec() time might be a
> good idea. It's just that nobody has gotten around to that
> yet...
SVR4 did and saw an improvement wrt. page fault rate, according to
Vahalia.
I'd like to see whether this is useful for Linux.
-- wli
next prev parent reply other threads:[~2003-03-17 14:59 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 [this message]
2003-03-17 16:01 ` Rik van Riel
2003-03-17 16:52 ` wind
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=20030317151004.GR20188@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=palbrecht@uswest.net \
--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 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.