All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Fokkens <rolf@rolffokkens.nl>
To: Zachary Palmer <zep_kernel.org@bahj.com>,
	"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: Is bcache dead?
Date: Thu, 06 Nov 2014 23:12:39 +0100	[thread overview]
Message-ID: <545BF257.6020708@rolffokkens.nl> (raw)
In-Reply-To: <545B8DDC.4070905@bahj.com>

Another happy user experience: I started packaging bcache-tools for 
Fedora 20 summer 2013, just because I wanted to use bcache. After 
alligning bcache-tools with util-linux, Dracut and LVM2 (all these 
packages needed minor tweaks, that were all integrated upstream) I have 
been using bcache myself (of course). I've been living on the edge by 
using writeback caching and a cheap SSD, and it has all been working 
like a charm! Well, I've been living over the edge actually by 
attempting to enable TRIM - I blame the resulting corruptions on the 
cheap SSD. And I had occasional "bcache_writeback 100% CPU" issues, but 
those seem to be gone (currently kernel 3.16).

And searching for bcache at bugzilla.redhat.com: no bugs pop up. Could 
be that there are no bcache users at all, but I know for fact that 
that's not true.

So (when not using TRIM): excellent performance and stability. Thanks 
for the good work!

Rolf

On 11/06/2014 04:03 PM, Zachary Palmer wrote:
> If I can throw mine in as well, I've been running bcache on my Debian 
> Wheezy laptop for around a year now.  (I'm using the Debian backports 
> 3.12 kernel.)  When I first moved to bcache, I noticed that certain 
> operations -- interacting with Git repositories and building LaTeX 
> documents, for instance -- became much snappier. I'm using a feeble 
> little 32GB SSD that came with the laptop to cache a 1TB drive and I'm 
> even using writethrough caching (more out of paranoia about the 
> quality of my cheap little SSD than anything else), but it makes a 
> difference.
>
> Since then, it has been quietly humming along and I've stopped paying 
> attention to it.  And that's the beauty of a good tool like this: I 
> can stop paying attention to it.  I've enjoyed a year of better I/O 
> and, other than in the initial setup, I haven't paid anything in 
> maintenance burden: no instability, no hiccups, no unexplained hangs.  
> So for my part as an end user just trying to get a little edge out of 
> my laptop hardware, thank you!  I expect I'm speaking on behalf of 
> quite a few people when I say that you've made things better in a 
> subtle but significant way.  :)
>
> Cheers,
>
> Zach

  reply	other threads:[~2014-11-06 22:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 12:07 Is bcache dead? Stefan Priebe - Profihost AG
2014-10-30 14:09 ` Vasiliy Tolstov
2014-10-30 14:14   ` Stefan Priebe - Profihost AG
2014-10-30 14:15     ` Kent Overstreet
2014-10-30 14:18       ` Stefan Priebe - Profihost AG
2014-10-30 15:58         ` Thomas Stein
2014-10-30 14:14 ` Kent Overstreet
2014-10-30 14:15   ` Stefan Priebe - Profihost AG
2014-10-30 19:55   ` Stan Hoeppner
2014-10-30 23:34     ` Kent Overstreet
2014-11-06 15:03       ` Zachary Palmer
2014-11-06 22:12         ` Rolf Fokkens [this message]
2015-01-19 18:36         ` Michael Russo

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=545BF257.6020708@rolffokkens.nl \
    --to=rolf@rolffokkens.nl \
    --cc=linux-bcache@vger.kernel.org \
    --cc=zep_kernel.org@bahj.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.