On Sun, 2016-11-06 at 09:35 +0200, Sagi Grimberg wrote: > > > > Btw, I want to actually make the ctrlid global for the target > > instead of > > per-subsystem to ease a few things, and debuggability is just one > > more > > on the list. How will that be NVMe-over-Fabrics spec compliant? The way I interpret the spec, ctrlid (I'm assuming you mean cntlid) is allocated on a NVM subsystem basis. For example, Figure 34 of the Discovery Log Page entry and Figure 20 of the Connect Command implies to me CNTLID values are allocated on a NVM Subsystem granular-level when I see statements such as: (Figure 20: Connect Command Data): "...If the NVM subsystem uses the static controller model and the value is FFFEh for the Admin Queue, then any available controller may be returned." This implies to me cntlid are allocated on an NVM subsystem basis, not an NVMe Target basis. > > Sounds good > > _______________________________________________ > Linux-nvme mailing list > Linux-nvme@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/linux-nvme -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
