On 8/25/2015 4:35 AM, Achiad Shochat wrote:
On 8/24/2015 11:40 PM, Tom Talpey wrote:
On 8/20/2015 12:46 PM, Achiad Shochat wrote:
Hi Doug,
This patchset adds RoCE V1 and RoCE V2 support to the mlx5 device
driver.
Question - assuming I read them correctly, these patches add the
RoCE v1 and RoCE v2 support on a per-port basis. That is, a port
can be either IB, RoCE v1 or RoCE v2, but not a combination.
Has any thought been put toward supporting these protocols on a
per-QP basis, i.e. the caller of rdma_connect() can specify the
desired protocol? Or to have some sort of discovery?
I know that there may be implementation restrictions on today's
devices, but it's my personal belief that future devices will
support multiple protocols (perhaps beyond the three above), and
laying the groundwork for this today will be important.
Tom.
RoCE v1 and RoCE v2 are supported on a per-GID basis, not sure what got
you to understand it is per-port.
Because the protocol capabilities were being marked at the ib_device
level. Ok, it's good that the protocol is per-endpoint.
But I don't understand how it will work per-GID. What if the target
node is RoCEv2 and on another subnet? How will it discover the remote's
capability and establish the right protocol? How does the initiator
select the protocol, if there is a choice?
Another way of asking this question is, why is all this stuff in the
driver, at the bottom of the stack? I think it should be in the
rdmacm layer.
Tom.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
