On Tue, Sep 08, 2015 at 03:32:11PM +0300, Sagi Grimberg wrote: > The CM is responsible of establishing an RDMA channel. What you are > referring to is a concept of a session. I'm not entirely sure how we can > fit a model where the CM establishes a multi-channel session as the > CM request contains a (single) source QPN. So there is a 1-1 > relationship between a cm_id and a queue-pair. The device handle depends > on the address resolution to the end-node. > > I assume we can think of some form of an rdma_session which will manage > multiple cm_id's (that belongs to a single address resolution), call > the ULP to allocate their corresponding queue-pairs and send a connect > request for each one. Such an rdma_session can verify the same ib_device > handle on all the cm_id's. But I'm not sure how such a concept would > impact on aspects such as event handling etc...
What I'm more interested in is a way to tell the CM that I only want routes that are using this ib_device that I got from the first lookup as all others are useless for me. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
