I need to check on this. You may want to look at section A3.2.3 of
the spec.
If you set the first byte (network order) to 0x00, and the 2nd byte
to 0x01,
then you hit a 'reserved' range that probably isn't being used
currently.
If you don't care what the service ID is, you can specify 0, and the
kernel will
assign one. The assigned value can be retrieved by calling
ib_cm_attr_id().
(I'm assuming that you communicate the IDs out of band somehow.)
Ok; we'll need to check into this. I don't remember the ordering --
we might actually be communicating the IDs before calling
ib_cm_listen() (since we were simply using the PIDs, we could do that).
Thanks for the tip! Pasha -- can you look into this?
It looks that th modex message we are preparing during query stage, so
the order looks ok.
Unfortunately on my machines ibcm module does not create
"/dev/infiniband/ucm*" and I can not thest the functionality.
Regards,
Pasha.
