From: Alasdair G Kergon <agk@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: Device-mapper for write monitoring
Date: Thu, 19 Feb 2009 14:49:18 +0000 [thread overview]
Message-ID: <20090219144918.GC3962@agk.fab.redhat.com> (raw)
In-Reply-To: <OF2FA15171.EBB61656-ONC2257562.00256C52-C2257562.002C88F5@il.ibm.com>
On Thu, Feb 19, 2009 at 10:06:26AM +0200, Michael Keller wrote:
> For our block-based incremental backup software we need to monitor all
> writes to a device, and report them to our user mode application for
> further processing.
Sounds like a variant of dm snapshot code.
What precisely do you need?
Notification of every block every time it is changed?
Or just a list of all the blocks that changed within a defined period (i.e.
since the last backup)?
> 3. Are the interfaces of the device mapper relatively stable? (Assume that
> our target is not general enough to be included into mainline, and we'll
> have to do the API chasing ourselves.)
If integrated nicely into dm, it'll go upstream.
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2009-02-19 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 8:06 Device-mapper for write monitoring Michael Keller
2009-02-19 14:28 ` malahal
2009-02-22 13:18 ` Michael Keller
2009-02-23 5:48 ` malahal
2009-02-19 14:49 ` Alasdair G Kergon [this message]
2009-02-22 13:28 ` Michael Keller
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=20090219144918.GC3962@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@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.