public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.64-mm6
Date: Thu, 13 Mar 2003 11:32:09 -0800	[thread overview]
Message-ID: <20030313113209.0be9f71c.akpm@digeo.com> (raw)
In-Reply-To: <p73n0jz4cdt.fsf@amdsimf.suse.de>

Andi Kleen <ak@suse.de> wrote:
>
> Andrew Morton <akpm@digeo.com> writes:
> 
> 
> >   This means that large cache-cold executables start significantly faster.
> >   Launching X11+KDE+mozilla goes from 23 seconds to 16.  Starting OpenOffice
> >   seems to be 2x to 3x faster, and starting Konqueror maybe 3x faster too. 
> >   Interesting.
> > 
> >   This might cause weird thing to happen, especially on small-memory machines.
> 
> That's great. It would be nice to have this as a sysctl or perhaps
> some heuristic based on file size and available memory for 2.6.
> 

We shouldn't be putting this in-kernel, really.  Userspace can obtain
the same results by running madvise(MADV_WILLNEED) against the mapping
immediately after setting it up.  So a simple

	map = mmap(...);
+	if (getenv("MAP_PREFAULT"))
+		madvise(map, len, MADV_WILLNEED);

in glibc is enough.

That will work on 2.4, too.  I haven't tested that though.


  reply	other threads:[~2003-03-13 19:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030313032615.7ca491d6.akpm@digeo.com.suse.lists.linux.kernel>
2003-03-13 13:36 ` 2.5.64-mm6 Andi Kleen
2003-03-13 19:32   ` Andrew Morton [this message]
2003-03-13 21:49 2.5.64-mm6 Felipe Alfaro Solana
2003-03-14  0:23 ` 2.5.64-mm6 Thomas Molina
  -- strict thread matches above, loose matches on Subject: below --
2003-03-13 13:42 2.5.64-mm6 Felipe Alfaro Solana
2003-03-13 11:26 2.5.64-mm6 Andrew Morton
2003-03-13 16:23 ` 2.5.64-mm6 Jeremy Fitzhardinge
2003-03-13 19:34   ` 2.5.64-mm6 Andrew Morton
2003-03-14  3:04     ` 2.5.64-mm6 Steven Cole
2003-03-14  3:28       ` 2.5.64-mm6 Andrew Morton
2003-03-14  3:46         ` 2.5.64-mm6 Shawn
2003-03-14  3:51           ` 2.5.64-mm6 Andrew Morton
2003-03-14  3:56           ` 2.5.64-mm6 Robert Love
2003-03-14 13:31         ` 2.5.64-mm6 jlnance
2003-03-14 20:05           ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:10             ` 2.5.64-mm6 Alex Tomas
2003-03-14 20:22               ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:19                 ` 2.5.64-mm6 Alex Tomas
2003-03-13 20:35 ` 2.5.64-mm6 Thomas Molina
2003-03-14  9:29 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 11:55   ` 2.5.64-mm6 Andrew Morton
2003-03-15  8:38     ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 12:01 ` 2.5.64-mm6 Helge Hafting
2003-03-14 12:14   ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:38 ` 2.5.64-mm6 Eli Carter
2003-03-14 20:53   ` 2.5.64-mm6 Andrew Morton
2003-03-14 22:01     ` 2.5.64-mm6 Eli Carter
2003-03-14 22:21       ` 2.5.64-mm6 Andrew Morton

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=20030313113209.0be9f71c.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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