From: Kent Overstreet <kent.overstreet@gmail.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Andreas Herrmann <aherrmann@suse.com>,
Zdenek Kabelac <zkabelac@redhat.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
linux-bcache@vger.kernel.org
Subject: Re: dm-cache performance behaviour
Date: Wed, 6 Apr 2016 04:13:49 -0800 [thread overview]
Message-ID: <20160406121349.GA11587@kmo-pixel> (raw)
In-Reply-To: <20160405161226.GA17811@redhat.com>
On Tue, Apr 05, 2016 at 12:12:27PM -0400, Mike Snitzer wrote:
> Anyway, as Zdenek effectively: said dm-cache isn't a writecache. If you
> need a writecache then bcache is the only option as of now. Though
> there is an emerging DM writecache target that has stalled but can be
> revisited, see:
> http://git.kernel.org/cgit/linux/kernel/git/snitzer/linux.git/log/?h=writecache
bcache is still more than that, it's a combined read/writeback cache :) much
like how today we only have one pagecache for both read caching and write
caching. Main trick is you need a pretty sophisticated btree to pull that off
with good performance.
next prev parent reply other threads:[~2016-04-06 12:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 7:12 dm-cache performance behaviour Andreas Herrmann
2016-04-05 8:36 ` Zdenek Kabelac
2016-04-05 10:37 ` Pasi Kärkkäinen
2016-04-05 14:05 ` Andreas Herrmann
2016-04-05 16:12 ` Mike Snitzer
2016-04-06 11:58 ` Andreas Herrmann
2016-04-06 12:13 ` Kent Overstreet [this message]
2016-04-05 13:31 ` Andreas Herrmann
2016-04-05 14:16 ` Andreas Herrmann
2016-04-07 1:24 ` Eric Wheeler
2016-04-07 15:10 ` Vasiliy Tolstov
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=20160406121349.GA11587@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=aherrmann@suse.com \
--cc=dm-devel@redhat.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=zkabelac@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox