Linux Device Mapper development
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: dm-devel@redhat.com
Subject: [RFC] zodcache - auto-start dm-cache devices
Date: Fri, 18 Dec 2015 00:16:32 -0600	[thread overview]
Message-ID: <n508c1$8dl$1@ger.gmane.org> (raw)

https://github.com/ipilcher/zodcache

I've been looking for a "simple" way to manage dm-cache devices for a
while now -- something that operates a bit more like bcache than LVM
cache does, while still using the dm-cache infrastructure.  Having not
found anything, I finally created "zodcache".  (The name is mostly due
to wanting something that could be used as a magic number -- 20DCAC8E.)

Hopefully the README does a decent job of explaining how it works, so I
won't belabor it here:

   https://github.com/ipilcher/zodcache/blob/master/readme.pdf

I'm very interested in any feedback on this.

  * Is this approach useful?
  * Is there a better way of doing this?
  * Is the libdevmapper stuff in zcstart.c correct/optimal?

And now to sleep ...

Thanks!

-- 
========================================================================
Ian Pilcher                                         arequipeno@gmail.com
-------- "I grew up before Mark Zuckerberg invented friendship" --------
========================================================================

             reply	other threads:[~2015-12-18  6:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18  6:16 Ian Pilcher [this message]
2015-12-18  9:44 ` [RFC] zodcache - auto-start dm-cache devices Joe Thornber
2015-12-18 16:07 ` John Stoffel
2015-12-18 16:55   ` Ian Pilcher
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='n508c1$8dl$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox