From: Jens Axboe <axboe@suse.de>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: linux-kernel@vger.kernel.org, mason@suse.com
Subject: Re: [PATCH] fcache: a remapping boot cache
Date: Wed, 31 May 2006 08:12:35 +0200 [thread overview]
Message-ID: <20060531061234.GC29535@suse.de> (raw)
In-Reply-To: <4d8e3fd30605301438k457f6242x1df64df9bab7f8f1@mail.gmail.com>
On Tue, May 30 2006, Paolo Ciarrocchi wrote:
> On 5/16/06, Jens Axboe <axboe@suse.de> wrote:
> >On Mon, May 15 2006, Jens Axboe wrote:
> >> On Mon, May 15 2006, Jens Axboe wrote:
> >> > o Trying it on my notebook brought the time from the kernel starts
> >> > loading to kde has fully auto-logged in down from 50 seconds to 38
> >> > seconds. The primed boot took 61 seconds. The notebook is about 4
> >> > months old and the file system is very fresh, so better results
> >should
> >> > be seen on more fragmented installs.
> >>
> [...]
> >git://brick.kernel.dk/data/git/linux-2.6-block.git fcache
>
> Just cloned.
>
> Any progress on this project Jens?
>
> I'll try to apply the patch to mainline and post here some numbers.
Well it's a git repo, get it and see :-)
But yes, it's had various fixes and optimizations, it should apply to
latest Linus kernel. There's also a consistency checker here:
git://brick.kernel.dk/data/git/fcache.git
that can check both fcache data and metadata.
--
Jens Axboe
next prev parent reply other threads:[~2006-05-31 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 9:18 [PATCH] fcache: a remapping boot cache Jens Axboe
2006-05-15 10:10 ` Jens Axboe
2006-05-16 7:46 ` Jens Axboe
2006-05-30 21:38 ` Paolo Ciarrocchi
2006-05-31 6:12 ` Jens Axboe [this message]
2006-06-24 3:44 ` James
2006-06-24 11:10 ` Jens Axboe
2006-06-24 12:03 ` [ck] " André Goddard Rosa
2006-06-26 6:43 ` Jens Axboe
[not found] ` <fe15b94a0606260015i440c995vda3327cc3c4c8210@mail.gmail.com>
2006-06-26 7:21 ` Jens Axboe
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=20060531061234.GC29535@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=paolo.ciarrocchi@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