<p>Hi<br>
Just of pure curiosity, can you please provide a link to the blog you had mentioned?<br>
Regards<br>
Rami Rosen</p>
<p><a href="http://ramirose.wix.com/ramirosen">http://ramirose.wix.com/ramirosen</a></p>
<div class="gmail_quote">On May 6, 2013 10:46 PM, "neha naik" <<a href="mailto:nehanaik27@gmail.com" target="_blank">nehanaik27@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br> 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.<br>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,<br>
reading about the device mapper api i have started thinking that it may not be the case.<br>May be for stackable device drivers device mapper is the solution.<br>What do you think? What are the pros and cons of device mapper v/s block device driver<br>
<br>Regards,<br>Neha<br>
<br>_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org" target="_blank">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
<br></blockquote></div>