From: Ian Pilcher <arequipeno@gmail.com>
To: dm-devel@redhat.com
Subject: Re: [RFC] zodcache - auto-start dm-cache devices
Date: Fri, 18 Dec 2015 10:55:32 -0600 [thread overview]
Message-ID: <n51dq4$dit$1@ger.gmane.org> (raw)
In-Reply-To: <22132.12088.729694.12882@quad.stoffel.home>
On 12/18/2015 10:07 AM, John Stoffel wrote:
>>From my reading of the docs, it's clear that zodcache is lower down
> the stack than LVMcache, but higher than bcache.
I would actually say that zodcache is at about the same level as
bcache. The main conceptual difference is that zodcache does device
probing/recognition and setup are done in userspace, where bcache does
it in kernel space. (I.e. echo the device name to
/sys/fs/bcache/register and the kernel looks a the device, decides
what it is, etc.)
> So describinng how your setup can provide a central cache pool across
> multiple VGs would be awesome, but it's not quite clear to me that you
> can do this in reality without doing multiple layers of block devices.
Currently you'll need multiple zodcache devices to create multiple VGs.
It should be possible to make these devices partitionable with a udev
rule that calls kpartx as appropriate.
> And since I'm paranoid (to a degree!) about resiliency, mirroring the
> cache devices is a critical part for me.
I haven't yet tested zodcache on top of MD RAID, but I fully expect it
to work.
> Also, I'm on debian, so that's another piece of documentation that's
> kinda sorta missing.
What do you need beyond what's in section III-B of the README?
--
========================================================================
Ian Pilcher arequipeno@gmail.com
-------- "I grew up before Mark Zuckerberg invented friendship" --------
========================================================================
next prev parent reply other threads:[~2015-12-18 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 6:16 [RFC] zodcache - auto-start dm-cache devices Ian Pilcher
2015-12-18 9:44 ` Joe Thornber
2015-12-18 16:07 ` John Stoffel
2015-12-18 16:55 ` Ian Pilcher [this message]
2015-12-18 17:39 ` Ian Pilcher
2015-12-18 18:53 ` John Stoffel
2015-12-18 18:51 ` Alasdair G Kergon
2015-12-18 19:44 ` John Stoffel
2015-12-18 20:01 ` Alasdair G Kergon
2015-12-18 20:50 ` Ian Pilcher
2015-12-18 21:06 ` Zdenek Kabelac
2015-12-19 0:01 ` Ian Pilcher
2015-12-19 0:53 ` Never mind (was [RFC] zodcache - auto-start dm-cache devices) Ian Pilcher
2015-12-19 1:53 ` John Stoffel
2016-01-04 15:52 ` Joe Thornber
2016-01-06 15:49 ` Ian Pilcher
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='n51dq4$dit$1@ger.gmane.org' \
--to=arequipeno@gmail.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.