From: Rolf Fokkens <rolf@rolffokkens.nl>
To: dm-devel@redhat.com
Subject: Re: Status dm-cache
Date: Tue, 27 Aug 2013 12:50:25 +0200 [thread overview]
Message-ID: <521C8471.3090804@rolffokkens.nl> (raw)
In-Reply-To: <521C8075.7060903@redhat.com>
Thanks.
I'll defer integrating dm-cache in Fedora until LVM2 supports it.
Rolf
On 08/27/2013 12:33 PM, Zdenek Kabelac wrote:
> Dne 25.8.2013 23:46, Rolf Fokkens napsal(a):
>> Hi!
>>
>> I'm trying to package some tools for "SSD caching" for Fedora 20, see:
>> https://bugzilla.redhat.com/show_bug.cgi?id=998543
>>
>> bcache has some nice bcache-tools, and packaging progresses well:
>> https://bugzilla.redhat.com/show_bug.cgi?id=999690
>>
>> Packaging dm-cache however seems seems hard. I'm not aware of any
>> userland
>> tools, and using dm-cache (without them) seems quite complex. Looks
>> like all
>> kinds of math are needed to make it work, e.g. :
>> http://blog.kylemanna.com/linux/2013/06/30/ssd-caching-using-dmcache-tutorial/.
>>
>> - Is there a (well supported) toolset available that I'm missing?
>> - Is there any kind of autodetect possible, e.g. during boot?
>>
>> Any information on the status of dm-cache is appreciated.
>
>
> For direct usage of dm-cache target:
>
> linux/Documentation/device-mapper/cache.txt
> linux/Documentation/device-mapper/cache-policies.txt
>
> Userland tool here is dmsetup.
>
> There will be a direct support for dm cache device stacking in lvm2 in
> the future. It will use nearly the same code as is used for thin
> provisioning,
> so the code for now thinp is improved to handle recovery more
> autonomously first before the caching support will be added.
>
> Zdenek
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2013-08-27 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 21:46 Status dm-cache Rolf Fokkens
2013-08-27 10:33 ` Zdenek Kabelac
2013-08-27 10:50 ` Rolf Fokkens [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=521C8471.3090804@rolffokkens.nl \
--to=rolf@rolffokkens.nl \
--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.