From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: cache_mode none
Date: Thu, 4 Oct 2012 12:53:59 -0700 [thread overview]
Message-ID: <20121004195359.GC29494@google.com> (raw)
In-Reply-To: <20121004102406.GC17229-Z3X8UqLNtc1Swagx7F3lBaxOck334EZe@public.gmane.org>
On Thu, Oct 04, 2012 at 03:54:06PM +0530, Kingsly John wrote:
> Hi!
>
> I've been trying out bcache over the last couple of weeks and couldn't find
> this explained anywhere.
>
> On my setup here while writing with cache_mode set to none, there's a
> near constant 30-40kb/sec write happening to the flash device all through.
> But in the other modes the amount of data written is significantly
> higher.(While copying the same set of files into a freshly formatted bcache
> device)
>
> Does setting cache_mode to none just disable the cache for reading or does it
> disable it for both reading and writing?
>
> If it's only disabled for reads, then with cache_mode set to none would
> bcache still recover from an unclean shutdown?
In cache_mode none, nothing new will be added to the cache (neither from
writes nor cache misses), but the cache is still kept consistent -
that's the reason for the writing that still happens to the flash
devices, it's invalidating the cache whenever you do a write.
It will still read from the cache, because there might still be dirty
data in the cache.
prev parent reply other threads:[~2012-10-04 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 10:24 cache_mode none Kingsly John
[not found] ` <20121004102406.GC17229-Z3X8UqLNtc1Swagx7F3lBaxOck334EZe@public.gmane.org>
2012-10-04 19:53 ` 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=20121004195359.GC29494@google.com \
--to=koverstreet-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.