public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Tomas <bzzz@tmi.comex.ru>
To: wind@cocodriloo.com
Cc: Rik van Riel <riel@surriel.com>,
	linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: 2.4 vm, program load, page faulting, ...
Date: 17 Mar 2003 19:50:04 +0300	[thread overview]
Message-ID: <m3hea2gcoz.fsf@lexa.home.net> (raw)
In-Reply-To: <20030317165223.GA11526@wind.cocodriloo.com>

>>>>> wind  (w) writes:

 w> 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?
 >> > 

 w> You should ask Andrew about his patch to do exactly that: he
 w> forced all PROC_EXEC mmaps to be nonlinear-mapped and this forced
 w> all programs to suck entire binaries into memory...  I recall he
 w> saw at least 25% improvement at launching gnome.

they talked about pages _already present_ in pagecache.



  reply	other threads:[~2003-03-17 16:47 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
2003-03-17 16:50         ` Alex Tomas [this message]
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=m3hea2gcoz.fsf@lexa.home.net \
    --to=bzzz@tmi.comex.ru \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@surriel.com \
    --cc=wind@cocodriloo.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