From: Joe Thornber <thornber@redhat.com>
To: John Stoffel <john@stoffel.org>
Cc: Joe Thornber <ejt@redhat.com>, dm-devel@redhat.com
Subject: Re: [PATCH] [dm-cache] Make the mq policy an alias for smq
Date: Thu, 11 Feb 2016 10:10:02 +0000 [thread overview]
Message-ID: <20160211101001.GA4908@rh-vpn> (raw)
In-Reply-To: <22203.28152.788363.168128@quad.stoffel.home>
On Wed, Feb 10, 2016 at 12:06:00PM -0500, John Stoffel wrote:
>
> Can you add in some documentation on how you tell which dm_cache
> policy is actually being used, and how to measure it, etc? It's a
> black box and some info would be nice.
You can get some stats on the cache performance via the status ioctl
(eg, dmsetup status ...). This will tell you about
promotions/demotion to the cache, write hits, read hits etc.
There is documentation on cache policies in Documentation/device-mapper/cache-policies.txt
https://github.com/jthornber/linux-2.6/blob/2016-02-10-thin-dev-on-4.4/Documentation/device-mapper/cache-policies.txt
As for knowing which policy is running; I'm not sure what to say.
It'll be the one you ask for. If the above patch goes in, then
there'll be a kernel version where mq becomes the same as smq. I'll
bump the policy version number to make it clear that mq has undergone
a big change.
- Joe
next prev parent reply other threads:[~2016-02-11 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 10:35 [PATCH] [dm-cache] Make the mq policy an alias for smq Joe Thornber
2016-02-10 17:06 ` John Stoffel
2016-02-11 10:10 ` Joe Thornber [this message]
2016-02-11 20:32 ` John Stoffel
2016-02-11 2:13 ` Mike Snitzer
2016-02-11 10:00 ` Joe Thornber
2016-02-11 10:41 ` Joe Thornber
2016-02-26 22:03 ` Mike Snitzer
2016-02-27 8:18 ` Joe Thornber
2016-02-11 10:40 ` [PATCH] [dm-cache] " Joe Thornber
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=20160211101001.GA4908@rh-vpn \
--to=thornber@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).