Device mapper api v/s block device driver api
Hi, Reading a blog on device mapper api got me confused about when one should use device mapper api and when to use block device driver api. I was under the impression that even for stackable device drivers (say a customized block device driver on top of lvm or such) we need to use the block device driver api. But, reading about the device mapper api i have started thinking that it may not be the case. May be for stackable device drivers device mapper is the solution. What do you think? What are the pros and cons of device mapper v/s block device driver Regards, Neha
On Mon, 06 May 2013 13:37:50 -0600, neha naik said:
What do you think? What are the pros and cons of device mapper v/s block device driver
Block device driver does exactly one thing - provides a driver for a a generic block device. If all you need is a generic block device, use this. Device-mapper provides targets that do things other than a generic block device. Stuff like crypto support, logical block forwarding and mapping to support things like LVM, multipath support, software raid, caching, etc. Basically, look around in drivers/md at the already existing targets.
participants (2)
-
neha naik -
Valdis.Kletnieks@vt.edu