From: "Olivier B." <dm.list@daevel.fr>
To: dm-devel@redhat.com
Subject: Re: dm-cache module
Date: Sun, 21 Mar 2010 11:35:02 +0100 [thread overview]
Message-ID: <4BA5F656.4030108@daevel.fr> (raw)
In-Reply-To: <20100321033704.GA6448@redhat.com>
On 21/03/2010 04:37, Mike Snitzer wrote:
> Such a DM target would be quite useful to have upstream given how
> prevalent SSDs have become.
>
I'm totally agree with that.
> Just curious: where have you gotten this insight about dm-cache being
> stable and used in production? That should help dm-cache's cause if it
> is submitted for review.
>
Well I wrote to Ming before post here, and found comments about the
module in the project OpenFiler which seem to integrate it :
https://forums.openfiler.com/viewtopic.php?id=3595
> Writeback support is arguably the most useful aspect of a caching DM
> target so emphasis must be placed on its review/implementation. Using
> SSD as a persistent writeback cache should afford us much more fault
> tolerance in the face of system crashes during writeback to the slower
> media.
>
Yes it's also for the writeback feature I'm interested.
I don't think be enough skilled to help for update the code, but maybe I
can do some tests.
Thanks,
Olivier
next prev parent reply other threads:[~2010-03-21 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 0:03 dm-cache module Olivier B.
2010-03-21 3:37 ` Mike Snitzer
2010-03-21 10:35 ` Olivier B. [this message]
[not found] ` <15606e421003202156n21de56a6n868f84bf737cce51@mail.gmail.com>
2010-03-22 15:05 ` Heinz Mauelshagen
2010-04-28 1:33 ` Olivier B.
2010-04-28 8:21 ` Heinz Mauelshagen
2010-04-28 14:02 ` Heinz Mauelshagen
2011-06-03 19:16 ` Phillip Susi
2011-06-06 10:06 ` Heinz Mauelshagen
2012-12-11 21:49 ` Phillip Susi
2012-12-11 21:56 ` Alasdair G Kergon
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=4BA5F656.4030108@daevel.fr \
--to=dm.list@daevel.fr \
--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.