From: Mike Snitzer <snitzer@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 6/6] dm cache: add cache block invalidation support
Date: Tue, 12 Nov 2013 12:35:57 -0500 [thread overview]
Message-ID: <20131112173557.GA10829@redhat.com> (raw)
In-Reply-To: <20131112004633.GJ24324@agk-dp.fab.redhat.com>
On Mon, Nov 11 2013 at 7:46pm -0500,
Alasdair G Kergon <agk@redhat.com> wrote:
> On Mon, Nov 11, 2013 at 12:20:48PM -0500, Mike Snitzer wrote:
> > From: Joe Thornber <ejt@redhat.com>
>
> > Cache block invalidation is removing an entry from the cache without
> > writing it back. Cache blocks can be invalidated via the
> > 'invalidate_cblocks' message, which takes an arbitrary number of cblock
> > ranges:
> > invalidate_cblocks [<cblock>|<cblock begin>-<cblock end>]*
>
> If we're expecting to need to invalidate a large number of ranges, should we
> switch this over to hexadecimal like we did for dm-switch?
>
> Should we consider changing this to <cblock>+<length> as the dm
> interfaces tend to work with a start offset and a length?
>
> Or will it be that the userspace interface will not be the bottleneck in
> this code so it really doesn't matter about attempting to optimise that
> part?
TBD. Plan is to introduce "invalidate_cblocks_hex" variant if needed.
> > +++ b/Documentation/device-mapper/cache.txt
>
> > The test suite can be found here:
> > -https://github.com/jthornber/thinp-test-suite
> > +https://github.com/jthornber/device-mapper-test-suite
>
> It's really not good if URLs in existing documentation become invalid
> like this: Could an obvious pointer be placed at the old location to
> direct people to the new location?
>
> Can we document whether or not all the ranges will have been invalidated
> before the message returns?
>
> > + if (!passthrough_mode(&cache->features)) {
> > + DMERR("cache has to be in passthrough mode for invalidation");
>
> Can we document this too?
>
> > @@ -2841,6 +3054,12 @@ static int cache_message(struct dm_target *ti, unsigned argc, char **argv)
> > + if (!strcmp(argv[0], "invalidate_cblocks"))
>
> strcasecmp please!
Pushed the following commit to address your comments in this patchset,
can rebase this commit if you have any further suggestions:
http://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=e67df7acf867b654c6eca7d08ee0452e9c5e4534
next prev parent reply other threads:[~2013-11-12 17:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 17:20 [PATCH for-3.13 0/6] dm cache: simple cache block invalidation interface Mike Snitzer
2013-11-11 17:20 ` [PATCH 1/6] dm cache: cache shrinking support Mike Snitzer
2013-11-11 21:19 ` Alasdair G Kergon
2013-11-11 21:32 ` Mike Snitzer
2013-11-11 21:48 ` Alasdair G Kergon
2013-11-11 21:50 ` Mike Snitzer
2013-11-11 22:09 ` Alasdair G Kergon
2013-11-11 22:15 ` Alasdair G Kergon
2013-11-11 23:06 ` Mike Snitzer
2013-11-11 23:17 ` Alasdair G Kergon
2013-11-11 23:34 ` Mike Snitzer
2013-11-11 23:03 ` Alasdair G Kergon
2013-11-11 23:08 ` Mike Snitzer
2013-11-11 17:20 ` [PATCH 2/6] dm cache: add passthrough mode Mike Snitzer
2013-11-11 23:40 ` Alasdair G Kergon
2013-11-11 17:20 ` [PATCH 3/6] dm cache metadata: check the metadata version when reading the superblock Mike Snitzer
2013-11-11 17:20 ` [PATCH 4/6] dm cache policy mq: reduce memory requirements Mike Snitzer
2013-11-11 17:20 ` [PATCH 5/6] dm cache: add remove_cblock method to policy interface Mike Snitzer
2013-11-12 0:18 ` Alasdair G Kergon
2013-11-11 17:20 ` [PATCH 6/6] dm cache: add cache block invalidation support Mike Snitzer
2013-11-12 0:46 ` Alasdair G Kergon
2013-11-12 17:35 ` Mike Snitzer [this message]
2013-11-12 19:26 ` 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=20131112173557.GA10829@redhat.com \
--to=snitzer@redhat.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.