There is absolutely no point in dragging in an overcomplicated configfs structure for a very simple protocol which also is very different from SCSI in it's nitty gritty details. Keeping the nvme target self contains allows it to be both much simpler and much easier to understand, as well as much better testable - see the amount of test coverage we could easily add for example.
Or to put it the other way around - if there was any major synergy in reusing the SCSI target code that just shows we're missing functionality in the block layer or configfs. The only thing where this is the case mid-term is persistent reservations, but Mike Christie already has a plan for a pluggable PR API, which I'm very interested in. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
