On 3/26/2013 5:55 PM, Hefty, Sean wrote:
This is just a workaround I been considering in case using "hints" and
asynchronous connection request can't work together. If I want to have
servers and clients that need to be backward compatible with RC servers
and clients. And assuming the old ones didn't used the private data in
the connection request and in the accept. Than the presence of the
private data will indicated that these are XRC enabled clients and servers.
I don't see how an app can 'just switch' from RC to XRC without having coded
for the possibility of XRC. XRC introduces too many new concepts.
The communication is just one part of the application. It is acceptable
to prepare for both XRC and RC and decide ad-hoc which transport to use,
there is no intention to switch back and forth between the different
transport. The nature of the connection is to be established with the
connect-accept handshake, and it is not going to be changed as long as
the connection linger. So what I need is to accept connection requests
asynchronously and decide which transport module to uses.
S.P.
--
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
