linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: "Cédric Villemain" <cedric.villemain.debian@gmail.com>
Cc: linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: Bcache version 9
Date: Tue, 23 Nov 2010 22:25:21 -0800	[thread overview]
Message-ID: <4CECAFD1.10506@gmail.com> (raw)
In-Reply-To: <AANLkTim7_Lm3U+jHe7KG8Ha9rqe=jg2yffb8NA8RLiGM@mail.gmail.com>

On 11/23/2010 03:35 PM, Cédric Villemain wrote:
> First I am really happy to see this project appearing here.
>
> 2010/11/21 Kent Overstreet<kent.overstreet@gmail.com>:
>> Bcache is a patch to use SSDs to transparently cache arbitrary block
>> devices. Its main claim to fame is that it's designed for the
>> performance characteristics of SSDs - it avoids random writes and
>> extraneous IO at all costs, instead allocating buckets sized to your
>> erase blocks and filling them up seqentially. It uses a hybrid
>> btree/log, instead of a hash table as some other caches.
>
> Is it its main diff with flashcache ?
> https://github.com/facebook/flashcache/blob/master/doc/flashcache-doc.txt

Yeah. It's a more complex approach, but it's capable of significantly 
higher performance. Performance has regressed some lately (I've been 
concentrating on other things and don't really have the hardware for 
performance work), but a month or so ago it was benchmarking around 50% 
higher than flashcache, with mysql on an X25-E.

>
>>
>> It does both writethrough and writeback caching - it can use most of
>> your SSD for buffering random writes, which are then flushed
>> sequentially to the backing device. Skips sequential IO, too.
>>
>> Current status:
>> Recovering from unclean shutdown has been the main focus, and is now
>> working magnificantly - I'm having no luck breaking it. This version
>> looks to be plenty safe enough for beta testing (still, make backups).
>>
>> Proper discard support is in and enabled by default; bcache won't ever
>> write to the same location twice without issuing a discard to that
>> bucket.
>
>   Is it relative to Torn Page possible issue outline by flashcache devel ?

Kind of. Bcache isn't subject to that issue, but that's because bcache 
is cow and always strictly orders writes.

  reply	other threads:[~2010-11-24  6:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 14:09 Bcache version 9 Kent Overstreet
2010-11-22  1:09 ` Greg KH
2010-11-23  8:07   ` Kent Overstreet
     [not found]     ` <4CEB7648.8030000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-12-01  4:16       ` Greg KH
2010-12-04  3:24         ` Kent Overstreet
2010-12-16 11:21         ` Kent Overstreet
2010-11-23 23:35 ` Cédric Villemain
2010-11-24  6:25   ` Kent Overstreet [this message]
     [not found]     ` <4CECAFD1.10506-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-12-04  5:41       ` John Drescher

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=4CECAFD1.10506@gmail.com \
    --to=kent.overstreet@gmail.com \
    --cc=cedric.villemain.debian@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).