From: Kent Overstreet <kent.overstreet@gmail.com>
To: Andi Kleen <andi@halobates.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Bcache: version 4
Date: Tue, 04 May 2010 15:47:49 -0800 [thread overview]
Message-ID: <4BE0B225.2080308@gmail.com> (raw)
In-Reply-To: <87y6g03rf8.fsf@basil.nowhere.org>
On 05/04/2010 02:14 AM, Andi Kleen wrote:
> I read all of this email now and I still have no clue what exactly
> a 'bcache' is and why anyone would want one (and if one needs
> a large stick to handle it or not)
>
> Normally the 0/x series of a patch kit is supposed to contain that
> information.
>
> I know it's probably obvious to you, but it's not to most other readers.
>
> Consider adding some introduction?
Ah, whoops. "Block cache" - it uses one block device to cache another,
it's intended for SSDs. It's summarized decently in the documentation
patch, which if I'd thought harder would've been the first email...
http://thread.gmane.org/gmane.linux.kernel/979977
Second patch also has relevant commentary:
http://thread.gmane.org/gmane.linux.kernel/979978
http://thread.gmane.org/gmane.linux.kernel/979979
Currently all the necessary functionality for read only is close to
done, I'm now doing stress testing. I'm hoping to have it Stable For Me
and read/write done in a week or two, at which point it should be ready
for people to start playing with.
prev parent reply other threads:[~2010-05-04 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 0:12 [PATCH 0/3] Bcache: version 4 Kent Overstreet
2010-05-01 13:01 ` Valdis.Kletnieks
2010-05-01 18:43 ` Kent Overstreet
2010-05-04 10:14 ` Andi Kleen
2010-05-04 23:47 ` Kent Overstreet [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=4BE0B225.2080308@gmail.com \
--to=kent.overstreet@gmail.com \
--cc=andi@halobates.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