On Fri, Sep 29, 2017 at 05:59:50PM +0300, Leon Romanovsky wrote:
On Fri, Sep 29, 2017 at 10:46:51AM -0400, Dennis Dalessandro wrote:
All of this vnic stuff is a work in progress and we are incrementally
pushing things out. Iterative development, involving the community and all.
Can we get OPA-VNIC specification? Can we get OPA specification?
The Documentation/infiniband/opa_vnic.txt is not enough to really
implement anything on top of that or communicate with that.
For example, what are the values and relations for routing control? How
is entropy calculated?
You are putting a wrong interpretation to this patch.
EM provides the encapsulation configuration as in the opa_vnic documentation.
EM will be opensourced when it is ready (VNIC is development in progress).
As mentioned, this patch is a simple *debug* hook to that encapsulation
configuration and no more.
That is why it is put under DEBUGFS.
I do see valid reason in Jason's and your earlier comments that it should a
formal support to the admins.
But this patch was not mainly for that. I don't expect DEBUGFS to be turned on
in all deployments.
I understand the question whether or not this patch should be in the kernel
tree.
But it is a useful debug hook for debugging/triaging issues (similar to NIC
having debug hook read/write some register), and convenient to have it
available in the kernel than maintaining it separately.
Niranjana
Thanks
--
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
