All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-writeboost: Progress Report
Date: Mon, 13 Jan 2014 10:09:03 +0000	[thread overview]
Message-ID: <20140113100903.GA4984@debian> (raw)
In-Reply-To: <52D0F25D.6030904@gmail.com>

On Sat, Jan 11, 2014 at 04:27:25PM +0900, Akira Hayakawa wrote:
> Hi, DM Guys, 
> 
> This is the latest progress report of dm-writeboost.

Do you have any benchmarks yet?  Which situations does it out perform
bcache and dm-cache?

> 4. Add some codes to Joe's device-mapper-test-suite
> ---------------------------------------------------
> Joe maintains a testing framework in his Github repo.
> I merged some test codes for Writeboost but I don't work on this project
> recently. I will add more code later.

Thanks for adding to dmtest, you also did a couple of little tidy ups
that were useful to me.

> 5. Add regression tests under testing/ of my Github tree
> --------------------------------------------------------
> Joe's test-suite is really well-designed but it has too many things before stand-by.

I'm not sure what you mean here?

- Joe

  reply	other threads:[~2014-01-13 10:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11  7:27 dm-writeboost: Progress Report Akira Hayakawa
2014-01-13 10:09 ` Joe Thornber [this message]
2014-01-13 11:46   ` Akira Hayakawa
2014-01-13 15:14     ` Mike Snitzer
2014-01-13 21:03     ` Paul B. Henson
2014-01-19  1:16       ` Akira Hayakawa
2014-01-14 10:17     ` Joe Thornber
  -- strict thread matches above, loose matches on Subject: below --
2014-05-17 14:44 Akira Hayakawa
2014-05-23 13:14 ` Akira Hayakawa
2013-11-04  5:17 Akira Hayakawa
2013-11-17 11:23 ` Akira Hayakawa

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=20140113100903.GA4984@debian \
    --to=thornber@redhat.com \
    --cc=dm-devel@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 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.