All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: John Stoffel <john@stoffel.org>
Cc: device-mapper development <dm-devel@redhat.com>,
	Ian Pilcher <arequipeno@gmail.com>
Subject: Re: [RFC] zodcache - auto-start dm-cache devices
Date: Fri, 18 Dec 2015 20:01:22 +0000	[thread overview]
Message-ID: <20151218200122.GB25064@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <22132.25135.428253.845795@quad.stoffel.home>

On Fri, Dec 18, 2015 at 02:44:47PM -0500, John Stoffel wrote:
> How deep can you stack things like this before you run into problems?
> And it does seem like it would put a bunch of stress on the UDEV setup
> to asseble it all reliably.

It should all work recursively to any reasonable level including udev.

If such use became more common, we'd to look at ways of optimising it:
We've considered allowing stacking within a single VG before, but
there hasn't really been enough demand to give it any priority.

If, as suggested here, there are now going to be common situations
where it makes sense, we can look again at introducing a more streamlined
approach.

Alasdair

  reply	other threads:[~2015-12-18 20:01 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
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 [this message]
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=20151218200122.GB25064@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=arequipeno@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=john@stoffel.org \
    /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.