From: wind-lkml@cocodriloo.com
To: Alex Tomas <bzzz@tmi.comex.ru>
Cc: riel@surriel.com, akpm@digeo.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4 vm, program load, page faulting, ...
Date: Mon, 17 Mar 2003 18:38:51 +0100 [thread overview]
Message-ID: <20030317173851.GC11526@wind.cocodriloo.com> (raw)
In-Reply-To: <20030317171246.GB11526@wind.cocodriloo.com>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
On Mon, Mar 17, 2003 at 06:12:46PM +0100, wind-lkml@cocodriloo.com wrote:
> On Mon, Mar 17, 2003 at 07:50:04PM +0300, Alex Tomas wrote:
> > >>>>> 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.
>
> I wonder if this could be done by walking and faulting
> all pages at fs/binfmt_elf.c::elf_map just after do_mmap...
> will try it just now :)
OK, this is not tested, since I'm compiling it now... feel free
to correct :)
[-- Attachment #2: binfmt_elf.c.diff --]
[-- Type: text/plain, Size: 878 bytes --]
--- orig/fs/binfmt_elf.c Mon Mar 17 18:26:59 2003
+++ work/fs/binfmt_elf.c Mon Mar 17 18:26:31 2003
@@ -259,12 +259,23 @@ create_elf_tables(struct linux_binprm *b
static inline unsigned long
elf_map (struct file *filep, unsigned long addr, struct elf_phdr *eppnt, int prot, int type)
{
- unsigned long map_addr;
+ unsigned long map_addr, pgoff;
+ struct mm *mm;
down_write(¤t->mm->mmap_sem);
map_addr = do_mmap(filep, ELF_PAGESTART(addr),
eppnt->p_filesz + ELF_PAGEOFFSET(eppnt->p_vaddr), prot, type,
eppnt->p_offset - ELF_PAGEOFFSET(eppnt->p_vaddr));
+
+ /* preload elf image */
+
+ mm = current->mm;
+ addr = ELF_PAGESTART(addr);
+ for(pgoff = 0; pgoff < eppnt->p_filesz;){
+ do_mmap_pgoff(mm, filep, addr, PAGE_SIZE, prot, type, pgoff);
+ addr += PAGE_SIZE;
+ pgoff += PAGE_SIZE;
+ }
up_write(¤t->mm->mmap_sem);
return(map_addr);
next prev parent reply other threads:[~2003-03-17 17:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 4:59 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
2003-03-17 17:12 ` wind-lkml
2003-03-17 17:38 ` wind-lkml [this message]
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=20030317173851.GC11526@wind.cocodriloo.com \
--to=wind-lkml@cocodriloo.com \
--cc=akpm@digeo.com \
--cc=bzzz@tmi.comex.ru \
--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
all inboxes | Powered by JetHome®