From: Gregory Maxwell <gmaxwell@gmail.com>
To: Hans van den Bogert <gandalf@unit-westland.nl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: l2arc-like ability in btrfs
Date: Tue, 29 Dec 2009 18:09:10 -0500 [thread overview]
Message-ID: <e692861c0912291509o4b5cd170oc15f5472c73ae5d2@mail.gmail.com> (raw)
In-Reply-To: <1262127361.3705.9.camel@gandalfpc>
On Tue, Dec 29, 2009 at 5:56 PM, Hans van den Bogert
<gandalf@unit-westland.nl> wrote:
> Will btrfs in the future implement a read cache like zfs has with l2arc,
> following it's hybrid storage concept.
> This would take away the hassle of choosing what and what not should be
> on your SSD, it would speed up the things you do most. And not what you
> did a lot a week ago. It should be persistent between boots so your boot
> sequence would benefit too.
A useful link for those who don't track all the details of ZFS development:
http://blogs.sun.com/brendan/entry/test
prev parent reply other threads:[~2009-12-29 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 22:56 l2arc-like ability in btrfs Hans van den Bogert
2009-12-29 23:09 ` Gregory Maxwell [this message]
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=e692861c0912291509o4b5cd170oc15f5472c73ae5d2@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=gandalf@unit-westland.nl \
--cc=linux-btrfs@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