From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
Kent Overstreet <koverstreet@google.com>,
Amit Kale <akale@stec-inc.com>,
linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] bcache/dmcache/enhanceio bake-off
Date: Sat, 13 Apr 2013 17:09:25 +0100 [thread overview]
Message-ID: <20130413160925.GA5236@debian> (raw)
In-Reply-To: <20130411072239.GD8910@blackbox.djwong.org>
Hi Darrick,
On Thu, Apr 11, 2013 at 12:22:39AM -0700, Darrick J. Wong wrote:
> Hi all,
>
> Lately I've been having some fun playing with bcache, dmcache, and enhanceio.
I pushed some tweaks to the mq policy today to my thin-dev tree. They
show some improvements to these fio based tests.
In addition I've written a blog post trying to explain what's going on in dm-cache:
http://device-mapper.org/blog/2013/04/13/benchmarking-dm-cache-with-fio/
- Joe
next prev parent reply other threads:[~2013-04-13 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 7:22 bcache/dmcache/enhanceio bake-off Darrick J. Wong
2013-04-13 16:09 ` Joe Thornber [this message]
2013-04-13 19:33 ` Mike Snitzer
2013-04-15 13:55 ` Mike Snitzer
2013-04-16 8:23 ` Joe Thornber
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=20130413160925.GA5236@debian \
--to=thornber@redhat.com \
--cc=akale@stec-inc.com \
--cc=dm-devel@redhat.com \
--cc=koverstreet@google.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@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