From: Thomas Petazzoni <thomas.petazzoni@enix.org>
To: sjackman@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Replaying a list of blocks into the cache (BootCache)
Date: Wed, 25 Jan 2006 18:58:19 +0100 [thread overview]
Message-ID: <43D7BC3B.8000701@enix.org> (raw)
In-Reply-To: <5yWak-99-39@gated-at.bofh.it>
Hi,
[ Sorry, I'm reading linux-kernel through the newsgroup, so my reply may
not contain the correct references, and may break the threading. ]
Shaun Jackman a écrit :
> This made me think of the OS X BootCache feature, which saves the list
> of disk blocks accessed during the boot sequence and replays that
> list on the next boot. Is there anything like this in Linux?
This has been discussed 2 years ago on KernelTrap:
http://kerneltrap.org/node/2157
I don't know if there have been further developments in this area.
Sincerly,
Thomas
--
Thomas Petazzoni, thomas.petazzoni@enix.org
next parent reply other threads:[~2006-01-25 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5yWak-99-39@gated-at.bofh.it>
2006-01-25 17:58 ` Thomas Petazzoni [this message]
2006-01-25 16:56 Replaying a list of blocks into the cache (BootCache) Shaun Jackman
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=43D7BC3B.8000701@enix.org \
--to=thomas.petazzoni@enix.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjackman@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