Linux Device Mapper development
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Thomas Knauth <thomas.knauth@gmx.de>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: change tracking with block-level granularity using md
Date: Wed, 18 Dec 2013 09:35:45 +0100	[thread overview]
Message-ID: <52B15E61.4090807@suse.de> (raw)
In-Reply-To: <CABhLV00aksW6BzyNswVeytfUQ+q_7PWag1njYs-E=acqqbXoVA@mail.gmail.com>

On 12/18/2013 09:04 AM, Thomas Knauth wrote:
> Hello list,
> 
> I am the author of the following paper
> 
> https://www.usenix.org/conference/lisa13/technical-sessions/papers/knauth
> 
> just presented at LISA 2013. Folks at the conference expressed
> interested in seeing this merged into the official Linux kernel. I
> would like to gauge your opinion of whether this has a chance to
> actually be accepted.
> 
Well, you just implemented an asynchronous mirror with discrete
tools. Congratulations.
Using bitmaps for tracking modified blocks has been a standard
technique in RAID1 for ages.

(look for mdadm --write-behind and drivers/md/bitmap.c. It's not
actually _new_ ...)

Sorry for being sarcastic.

But nevertheless, your tool might actually be useful; tracking block
changes could have some benefit on other areas.

What you should be doing:
- Rename the thing (dm-linear is taken; maybe dm-bitmap ?)
- Use debugfs instead of /proc
- Proper formatting

And then send the code for review.

Or go for the full monty and break up dm-mirror to include your
bitmap code. But then you would need to come up with a way of
storing your bitmap on disk.
Which is where the _real_ fun starts.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2013-12-18  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18  8:04 change tracking with block-level granularity using md Thomas Knauth
2013-12-18  8:35 ` Hannes Reinecke [this message]
2013-12-20 16:35 ` 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=52B15E61.4090807@suse.de \
    --to=hare@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=thomas.knauth@gmx.de \
    /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