On 03/21/2014 08:37 AM, Christoph Hellwig wrote: > 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?
Hi Christoph, I imagine the layer to interact with a compatible SSD, that either uses SATA, NVMe or PCI-e as host interface. My original thought was to use some of device mapper logic (such as raid, prisoning, etc.) to implement some of the primitives. Maybe this is overkill, and its better to stuff it between the blk-mq drivers and the blk-mq layer. > > 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. Good point. > > 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. > Agree, an underlying driver is missing. My first plan is to get a draft firmware for the OpenSSD to be stable and expose its primitives (read/write/erase) up through the ATA/SCSI stack. Communicating using vendor specific codes. - Matias -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
