Sewn was supposed to be srqn but got spell checked Sent from my iPhone
On May 11, 2011, at 3:36 PM, Bob Pearson <rpear...@systemfabricworks.com> wrote: > There is a connection between the ini and TFT qps they have to exchange qpns > so that they can check them later > The sewn is also sent and used to route messages to the srq at the target > > Sent from my iPhone > > On May 11, 2011, at 2:08 PM, "Hefty, Sean" <sean.he...@intel.com> wrote: > >>>> I guess I need to go back and study the specs more to understand why the >>> QPN is in the REQ. >>> >>> I looked at the kernel headers; struct cm_req_msg and cm_rep_msg, and >>> they both contain the QP numbers. >> >> I was referring only to *why* the XRC TGT QP needed to know the XRC INI QPN >> (at a conceptual level). I think it's for control messages. >> >>>> The REQ/REP also carry EECN fields which might be usable here, and maybe >>> that was the intent. >>> >>> The XRC spec does not make room for the srq number. Which implies it's left >>> to the application to transmit it. >> >> Agreed - I was wondering if using the EECN would work, but I don't think >> that it does. There would typically be multiple SRQs targeted by a single >> XRC INI->TGT connection. Maybe SIDR could be adopted for this purpose as >> the standard discovery technique. >> >> - Sean >> -- >> 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 > -- > 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 -- 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