From: Lauri Niskanen <ape@ape3000.com>
To: dm-devel@redhat.com
Subject: dm-cache with a very slow device
Date: Fri, 7 Aug 2015 08:39:21 +0300 [thread overview]
Message-ID: <55C44489.2050101@ape3000.com> (raw)
Hi,
In my understanding dm-cache is usually used with fairly fast spinning
hard drives as the "slow" device. Because of this the cache is not used
very aggressively and sequential accesses skip the cache. Is it possible
to configure dm-cache for a scenario where the fast disk is a
state-of-the-art SSD, but the slow disk is very slow especially so that
sequential reads and writes are significantly slower than on the fast
device?
I'd like it to work as a very aggressive writeback buffer, so that all
or at least close to all writes are done to the fast device if there is
at least some free non-dirty space left. And sequential reads should
also be promoted fairly easily. In addition there should be aggressive
demotions to make room for future promotions always keeping a sizable
buffer available.
So the goal would be to achieve the performance characteristics of the
fast device for all kinds of use cases even when the backing slow device
is at least a magnitude slower.
--
Lauri Niskanen
next reply other threads:[~2015-08-07 5:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 5:39 Lauri Niskanen [this message]
2015-08-07 15:10 ` dm-cache with a very slow device Mike Snitzer
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=55C44489.2050101@ape3000.com \
--to=ape@ape3000.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.