Roland Dreier wrote:
> Can you add the RAW_ETY qp type in this release as well?
To be honest I haven't looked at the iWARP datagram stuff at all. I'm
not sure overloading the RAW_ETY QP type is necessarily the right thing
to do -- it has quite different (never implemented) semantics in the IB
case. Is there any overview of what you guys are planning as far as
how work requests are created for such QPs?
The RAW_ETY qp would be just that: A kernel-bypass/user mode qp that
allows sending/receiving ethernet packets. It would also provide a way
for user applications to join/leave ethernet mcast groups (which
requires an rdma core kernel change that Intel posted too). What the
iWARP vendors are doing on top of that is implementing some form of UDP
in user mode. The main goal here is to provide an ultra low latency UDP
multicast and unicast channel for important market segments that desire
this paradigm. Also, due to the nature of this (send/recv raw eth
frames), the interface would be privileged.
If you want to wait, then later I'll post patches on how this is being
done for cxgb4. But I thought adding the RAW_ETY was definitely a
common requirement for Intel and Chelsio.
Steve.
--
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
