On Tuesday June 16, heinzm@xxxxxxxxxx wrote: > > That being said: once the future work on a unified virtual block device > infrastructure is production ready, we're open to use that. > I was kind-a hoping that you (and others) would be involved in developing this unified infrastructure, rather than just waiting for it. I think a great first step would be to allow md/raid5 to be used directly as a dm target, thus turning dm-raid5 into a shim layer over md/raid5. The process of doing this would very likely highlight a lot of the issues we would need to address in creating a unified framework. I will try to find time to review your dm-raid5 code with a view to understanding how it plugs in to dm, and then how the md/raid5 engine can be used by dm-raid5. Part of this will be disconnecting the md/raid5 code from any specific knowledge of a gendisk and a request_queue as I suppose a dm-target doesn't own any of these. Also I would probably want the mddev not be have to be on the "all_mddevs" list, as we would not want a 'dm' raid5 to appear in /proc/mdstat. NeilBrown -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
