From: Nikita Danilov <nikita@clusterfs.com>
To: Ram Gupta <ram.gupta5@gmail.com>
Cc: Michael Loftis <mloftis@wgops.com>,
"Barry K. Nathan" <barryn@pobox.com>, Al Boldi <a1426z@gawab.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] VM: I have a dream...
Date: Tue, 24 Jan 2006 18:11:38 +0300 [thread overview]
Message-ID: <17366.17322.923958.838500@gargle.gargle.HOWL> (raw)
In-Reply-To: <728201270601240636p58fead78m781fb104c3d73da9@mail.gmail.com>
Ram Gupta writes:
> On 1/23/06, Nikita Danilov <nikita@clusterfs.com> wrote:
>
> >
> > The unique feature that Mac OS X VM does have, on the other hand, is
> > that it keeps profiles of access patterns of applications, and stores
> > then in files, associated with executables. This allows to quickly
> > pre-fault necessary pages during application startup (and this makes OSX
> > boot so fast).
>
> This feature is interesting though I am not sure about the fast boot
> part of OSX.
> as at boot time these applications are all started first time. So
> there were no access pattern as yet. They still have to be demand
That's the point: information about access patterns is stored in the
file. So next time when application is started (e.g., during boot)
kernel reads that file and pre-faults pages.
> paged. But yes later accesses may be faster.
>
> Thanks
> Ram gupta
Nikita.
next prev parent reply other threads:[~2006-01-24 15:11 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 18:08 [RFC] VM: I have a dream Al Boldi
2006-01-21 18:42 ` Jamie Lokier
2006-01-21 18:46 ` Avi Kivity
2006-01-23 19:52 ` Bryan Henderson
2006-01-25 22:04 ` Al Boldi
2006-01-26 19:18 ` Bryan Henderson
2006-01-27 16:12 ` Al Boldi
2006-01-27 19:17 ` Bryan Henderson
2006-01-30 13:21 ` Al Boldi
2006-01-30 13:35 ` Kyle Moffett
2006-01-31 15:56 ` Al Boldi
2006-01-31 16:34 ` Kyle Moffett
2006-01-31 23:14 ` Bryan Henderson
2006-01-31 16:34 ` Lennart Sorensen
2006-01-31 19:23 ` Jamie Lokier
2006-02-01 4:06 ` Barry K. Nathan
2006-02-01 9:51 ` Andrew Walrond
2006-02-01 17:51 ` Lennart Sorensen
2006-02-01 18:21 ` Andrew Walrond
2006-02-01 18:25 ` Lennart Sorensen
2006-02-02 15:11 ` Alan Cox
2006-02-02 18:59 ` Al Boldi
2006-02-02 22:33 ` Bryan Henderson
2006-02-03 14:46 ` Alan Cox
2006-01-30 16:49 ` Bryan Henderson
2006-01-26 0:03 ` Jon Smirl
2006-01-26 19:48 ` Bryan Henderson
2006-01-22 8:16 ` Pavel Machek
2006-01-22 12:33 ` Robin Holt
2006-01-23 18:03 ` Al Boldi
2006-01-23 18:40 ` Valdis.Kletnieks
2006-01-23 19:26 ` Benjamin LaHaise
2006-01-23 19:40 ` Valdis.Kletnieks
2006-01-23 22:26 ` Pavel Machek
2006-01-22 19:55 ` Barry K. Nathan
2006-01-23 5:23 ` Michael Loftis
2006-01-23 5:46 ` Chase Venters
2006-01-23 8:20 ` Barry K. Nathan
2006-01-23 13:17 ` Jamie Lokier
2006-01-23 20:21 ` Peter Chubb
2006-01-23 15:05 ` Ram Gupta
2006-01-23 15:26 ` Diego Calleja
2006-01-23 16:11 ` linux-os (Dick Johnson)
2006-01-23 16:50 ` Jamie Lokier
2006-01-24 2:08 ` Horst von Brand
2006-01-25 6:13 ` Jamie Lokier
2006-01-25 9:23 ` Bernd Petrovitsch
2006-01-25 9:42 ` Lee Revell
2006-01-25 15:02 ` Jamie Lokier
2006-01-25 23:24 ` Lee Revell
2006-01-25 15:05 ` Jamie Lokier
2006-01-25 15:47 ` Bernd Petrovitsch
2006-01-25 16:09 ` Diego Calleja
2006-01-25 17:26 ` Jamie Lokier
2006-01-26 19:13 ` Bryan Henderson
2006-01-25 23:28 ` Lee Revell
2006-01-26 1:29 ` Diego Calleja
2006-01-26 5:01 ` Jamie Lokier
2006-01-26 5:11 ` Lee Revell
2006-01-26 14:46 ` Dave Kleikamp
2006-01-24 2:10 ` Horst von Brand
2006-01-25 22:27 ` Nix
2006-01-26 15:13 ` Denis Vlasenko
2006-01-26 16:23 ` Nix
2006-01-23 20:43 ` Michael Loftis
2006-01-23 22:42 ` Nikita Danilov
2006-01-24 14:36 ` Ram Gupta
2006-01-24 15:04 ` Diego Calleja
2006-01-24 20:59 ` Bryan Henderson
2006-01-24 15:11 ` Nikita Danilov [this message]
2006-01-23 22:57 ` Ram Gupta
2006-01-24 10:08 ` Meelis Roos
2006-02-01 13:58 Al Boldi
2006-02-01 14:38 ` Jamie Lokier
2006-02-02 12:26 ` Al Boldi
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=17366.17322.923958.838500@gargle.gargle.HOWL \
--to=nikita@clusterfs.com \
--cc=a1426z@gawab.com \
--cc=barryn@pobox.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mloftis@wgops.com \
--cc=ram.gupta5@gmail.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;
as well as URLs for NNTP newsgroup(s).