Just curious: why do you think implementing this as a block remapper inside device mapper is a better idea than as a blk-mq driver? At the request layer you already get a lot of infrastucture for all the queueing infrastructure for free, as well as all kinds of other helpers. And the driver never remaps bios anyway but always submits new ones as far as I can tell. Does it even make sense to expose the underlying devices as block devices? It surely would help to send this together with a driver that you plan to use it on top of. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
