dm-devel-bounces@xxxxxxxxxx wrote on 19/02/2009 16:49:18: > Re: Device-mapper for write monitoring > Alasdair G Kergon > to: > device-mapper development > 19/02/2009 16:50 > Cc: > Mikulas Patocka > > 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)? Our application is historically designed such that the bitmap is kept in (and accessed only by) user mode. If there is any general behavior in this (which would be worth including into dm...) it would be a kind of "user-intercept": let a user application register with the device, and get signaled (complete a pending read) for each write (or read) to the device. The user then decides what to do about it, and informs the kernel (e.g., filter, proceed, read-before-write, ...) > > 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. I'd wish. But as I said, I find it hard to see anything general in what we're doing. If you have ideas, let me know! Thanks, Michael > > Alasdair > -- > agk@xxxxxxxxxx > > -- > dm-devel mailing list > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
