RFC nvmet: Add support for multi-tenant configfs
Get series with b4
b4 am [email protected]Versions newest first
- v2 RFC Latest0 of 11 patches 0 repliesNew
Patches in v2 No applies recorded yet
None of the 11 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [RFC-v2 00/11] nvmet: Add support for multi-tenant configfs
Quoted 1 line · Nicholas A. Bellinger
Comments..?
Still no good reason for doing anything like this.
On a conceptual level:
The NVMe target is front end implementing a simple protocol to export block devices to a remove host. The SCSI target is larger front end to expose a more complex protocol to remote hosts. None of them should actually implement any real protocol independent behavior, and except for persistent reservations in the SCSI neither of them does.
On a practical level it means we drag in over 25.000 lines of code as a dependency, without actually dropping any code in the nvmet module, and vastly more complicated object hierarchies that don't make any sense for the tight-knit NVMe standard. We'd also get dragged into into the nightmare of diverging an incompatible user space tooling, and we'd lose all the test coverage we've built up. We'd also have to deal with tons of tunables that neither fit the protocol we implement nor the philosophy of the project.