From: Paul B. Henson <henson@acm.org>
To: lvm-devel@redhat.com
Subject: cache support
Date: Wed, 5 Feb 2014 17:36:23 -0800 [thread overview]
Message-ID: <0a7b01cf22db$da3f56c0$8ebe0440$@acm.org> (raw)
In-Reply-To: <52F2AD44.8030006@redhat.com>
> From: Zdenek Kabelac
> Sent: Wednesday, February 05, 2014 1:30 PM
>
> lvm2 is not supporting caching of PVs - that's the layer below the lvm2.
Your
> proposed idea would be hard to efficiently implement.
Hmm, yes, I see what you mean. I guess to go that way I'd have to use
dm-cache directly or reconsider bcache to create a cached device to feed to
lvm as a PV.
> We may consider the option to use a single cache pool for multiple single
> linear LVs - since in this case we might be able to resolve tricky virtual
> mapping.
It would probably work out for my use case if the PV itself wasn't cached
but the entire SSD cache device could be shared amongst all of the LV's. I
really don't want to split the cache into separate pieces per LV though,
that's just not going to scale.
Thanks.
next prev parent reply other threads:[~2014-02-06 1:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 1:51 cache support Paul B. Henson
2014-02-05 7:35 ` Oliver Rath
2014-02-05 20:12 ` Paul B. Henson
2014-02-05 9:35 ` Zdenek Kabelac
2014-02-05 20:20 ` Paul B. Henson
2014-02-05 21:29 ` Zdenek Kabelac
2014-02-06 1:36 ` Paul B. Henson [this message]
2014-02-11 17:24 ` Brassow Jonathan
2014-02-11 21:04 ` Paul B. Henson
2014-02-12 17:39 ` Brassow Jonathan
2014-02-17 22:12 ` Paul B. Henson
2014-03-11 23:54 ` Paul B. Henson
2014-03-17 15:56 ` Brassow Jonathan
2014-03-18 1:07 ` Paul B. Henson
2014-03-29 1:38 ` Paul B. Henson
2014-03-29 1:43 ` Paul B. Henson
2014-04-02 20:34 ` Brassow Jonathan
2014-04-03 2:54 ` Paul B. Henson
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='0a7b01cf22db$da3f56c0$8ebe0440$@acm.org' \
--to=henson@acm.org \
--cc=lvm-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.