[dm-devel] [PATCH RFCv2 01/10] dm-dedup: main data structures

Mike Snitzer snitzer at redhat.com
Wed Nov 26 15:38:34 UTC 2014


On Fri, Oct 17 2014 at  1:42pm -0400,
Mike Snitzer <snitzer at redhat.com> wrote:

> On Fri, Oct 17 2014 at  1:11pm -0400,
> Vasily Tarasov <tarasov at vasily.name> wrote:
> 
> > Hi Mike,
> > 
> > Sonam Mandal, who also works on dm-dedup project, has addressed your
> > comments about BUG() and BUG_ON(). She has also updated the code
> > related to mark and sweep. The changes are staged here (on top of your
> > dm-dedup repo):
> > 
> > git://git.fsl.cs.stonybrook.edu/scm/git/linux-dmdedup
> > branch: dm-dedup-devel
> > 
> > I'm not sure if you want us to send the patches to device-mapper
> > mailing list in addition to that. Let us know if we should do it.
> 
> I'll take a look next week, I need to finish up some dm-thinp work this
> week.  Your repo is perfect for now.
> 
> Thanks for doing this work.
> Mike

Hi Vasily,

I've been slammed with working on DM thinp and DM cache.  High priority
issues got elevated and we're only now putting those issues to rest.

So that said, I'll have time to focus on dm-dedup review starting next
week.  BUT this time it is different in that I'll be working closely
with Vivek Goyal (cc'd).  Vivek just joined Red hat's kernel storage
team and will be able to help with this review.  I'm asking Vivek to
focus on the meat of the dedup strategy you've deployed (algorithms,
etc).

I'll be maintain focus on the DM target mechanics (which should be in
good shape coming off the first cycle of review).

Apologies for DM dedup's review/inclusion slipping to the degree it
has.  I could've been much better about communicating my status.

Hopefully we can have DM dedup buttoned up and staged for upstream
inclusion in time for Christmas ;)

Mike




More information about the dm-devel mailing list