From: Mike Snitzer <snitzer@redhat.com>
To: Shaohua Li <shli@kernel.org>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
axboe@kernel.dk, agk@redhat.com
Subject: Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
Date: Mon, 10 Mar 2014 09:52:56 -0400 [thread overview]
Message-ID: <20140310135256.GA28665@redhat.com> (raw)
In-Reply-To: <20140307075733.GB21790@kernel.org>
On Fri, Mar 07 2014 at 2:57am -0500,
Shaohua Li <shli@kernel.org> wrote:
> ping!
Hi,
I intend to get dm-insitu-comp reviewed for 3.15. Sorry I haven't
gotten back with you before now, been busy tending to 3.14-rc issues.
I took a quick first pass over your code a couple weeks ago. Looks to
be in great shape relative to coding conventions and the more DM
specific conventions. Clearly demonstrates you have a good command of
DM concepts and quirks.
But one thing that would really help get dm-insitu-comp into 3.15 is to
show that the code is working as you'd expect. To that end, it'd be
great if you'd be willing to add dm-insitu-comp support to the
device-mapper-test-suite, see:
https://github.com/jthornber/device-mapper-test-suite
I recently added barebones/simple dm-crypt support, see:
https://github.com/jthornber/device-mapper-test-suite/commit/c865bcd4e48228e18626d94327fb2485cf9ec9a1
But It may be that activation/test code for the other targets (e.g. thin
or cache) are more useful examples to follow for implemnting
dm-insitu-comp stack activation, see:
https://github.com/jthornber/device-mapper-test-suite/blob/master/lib/dmtest/pool-stack.rb
https://github.com/jthornber/device-mapper-test-suite/blob/master/lib/dmtest/cache_stack.rb
All said, implementing dm-insitu-comp support for dmts (including some
tests that establish it is working as intended) isn't a hard requirement
for getting the target upstream but it would _really_ help.
Mike
next prev parent reply other threads:[~2014-03-10 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 10:13 Shaohua Li
2014-03-07 7:57 ` Shaohua Li
2014-03-10 13:52 ` Mike Snitzer [this message]
2014-03-14 9:40 ` Shaohua Li
2014-03-14 22:44 ` Mike Snitzer
2014-03-17 9:56 ` Shaohua Li
2014-03-17 20:00 ` Mike Snitzer
2014-03-18 7:41 ` Shaohua Li
2014-03-18 21:28 ` Mike Snitzer
2014-03-19 1:45 ` Shaohua Li
2014-03-19 16:16 ` 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=20140310135256.GA28665@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shli@kernel.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
Powered by JetHome