[PATCH 0/4] nvme-fabrics: add support for TP8010

[Sagi Grimberg]

> From: Martin Belanger <martin.belanger at dell.com>

Hey Martin,

> TP8010 defines the Central Discovery Controller (CDC). To tell a CDC
> apart from a DDC (Direct Discovery Controller), the Identify response
> now carries a Discovery Controller Type (dctype) attribute.
> 
> TP8010 also defines a new Discovery Information Management (DIM) PDU
> which is used to perform explicit registration with CDCs and DDCs.
> This new PDU carries extra information such as the Entity Name (ENAME),
> the Entity Version (EVER), the Symbolic Name, etc.
> 
> This set of patches adds support for TP8010 by exposing the dctype
> through the sysfs. It also adds the following two new configuration
> parameters:
> 
> 1) "register" - This is used to tell the kernel that the user
> wants to perform explicit registration using the DIM PDU. Without
> this, the driver will operate as it did before.
> 
> 2) "hostsymname" - This is used to specify an optional Symbolic Name.

I think that both Hannes and I share the stand that all of this needs
to live outside the kernel. Is there a fundamental reason to why you
chose to place this functionality in the kernel and expose a "register"
verb instead of simply doing this in nvme-cli (or a different utility)
to assemble the register command and issue it on an established
discovery controller?