[openib-general] UC connection server
Hi, I wonder if anybody could give some advice about an idea for making UC connections with a device that doesn't support a CM (it's a custom-made embedded device). The idea is to use a PC-based stack that does use the standard CM interface. I can then make a connection with that. The PC then gets the info about the real QP from the embedded device via some proprietary method. The problem with this idea is that in the standard CM protocol, it forms the connection using the LID that the REQ was sent to. But I need to change this to the LID of the embedded device. I've looked at doing path migration which looked like it might do this, but I could do with some advice. For example, in path migration, does the original connection remain? Any other suggests are welcome (I know I could do an Ethernet connection with the PC and exchange the info that way, but that's a last resort at the moment). Thanks for your time. Cheers, Steve. ___ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
Re: [openib-general] UC connection server
Hi Steve, On 12/6/05, Steven Wooding [EMAIL PROTECTED] wrote: Hi, The idea is to use a PC-based stack that does use the standard CM interface. I can then make a connection with that. The PC then gets the info about the real QP from the embedded device via some proprietary method. The problem with this idea is that in the standard CM protocol, it forms the connection using the LID that the REQ was sent to. Actually, it's the other way around. The CM uses the LID from the path information in the REQ as the destination of the MAD. There is no way currently to send a CM REQ to another LID than the one indicated in the REQ's path information. But I need to change this to the LID of the embedded device. I've looked at doing path migration which looked like it might do this, but I could do with some advice. No, path migration will only work accross ports of a single HCA. - Fab ___ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
Re: [openib-general] UC connection server
On 12/6/05, Sean Hefty [EMAIL PROTECTED] wrote: Steven Wooding wrote: The idea is to use a PC-based stack that does use the standard CM interface. I can then make a connection with that. The PC then gets the info about the real QP from the embedded device via some proprietary method. You can use the existing connection to exchange the QP information, similar to how you would exchange the information over Ethernet. Once the other QPs are setup, you can either teardown the existing connection or use it to connect other QPs. I think what Steve wants to do is issue a REQ, send it to the PC, but have the path record go to his embedded device (which has a different LID). The CM protocol supports this, but the implementation of the CM looks at the path record to determine the destination of the CM MADs. Supporting this would require some way for the user to set the target of the CM MADs independently of the path information contained in the REQ. Adding an optional extra path record for the CM path might do the trick. - Fab ___ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
Re: [openib-general] UC connection server
Hi Fabain, I think what Steve wants to do is issue a REQ, send it to the PC, but have the path record go to his embedded device (which has a different LID). The CM protocol supports this, but the implementation of the CM looks at the path record to determine the destination of the CM MADs. Supporting this would require some way for the user to set the target of the CM MADs independently of the path information contained in the REQ. Adding an optional extra path record for the CM path might do the trick. That's it in a nutshell really. I don't know how useful such a feature would be in the wider IB community. We've been forced into this position by a vendor not following the standard. I wanted to check with you guys whether there was a quick solution that was ready to fly. It seems that this feature would need to go into the openib drivers, which we don't have time or money to do. We do have a backup solution from the vendor, but its non-standard and I was trying to keep our side of the interface use the standard. Anyway, thanks for your suggests. It's all useful info. Regards, Steve. ___ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
