The Infiniband Communication Manager will refuse to establish a connection if it believes the connection is already established. There is no immediately obvious way to ask it to tear down the existing connection and replace it; to issue a DREP we would need to know the local and remote communication IDs used for the previous connection setup. We can work around this by randomising the high-order bits of the queue pair number; these have no significance to the hardware, but are sufficient to convince the IB CM that this is a different connection.tags/v0.9.8
|
|
||
857 |
|
857 |
|
858 |
|
858 |
|
859 |
|
859 |
|
860 |
|
|
|
|
860 |
|
|
|
861 |
|
|
861 |
|
862 |
|
862 |
|
863 |
|
863 |
|
864 |
|
|
|
||
877 |
|
878 |
|
878 |
|
879 |
|
879 |
|
880 |
|
880 |
|
|
|
|
881 |
|
|
|
882 |
|
|
881 |
|
883 |
|
882 |
|
884 |
|
883 |
|
885 |
|
|
|
||
2529 |
|
2531 |
|
2530 |
|
2532 |
|
2531 |
|
2533 |
|
2532 |
|
|
|
2533 |
|
|
|
|
2534 |
|
|
2534 |
|
2535 |
|
2535 |
|
2536 |
|
2536 |
|
2537 |
|
|
|
||
422 |
|
422 |
|
423 |
|
423 |
|
424 |
|
424 |
|
425 |
|
|
|
426 |
|
|
|
|
425 |
|
|
|
426 |
|
|
427 |
|
427 |
|
428 |
|
428 |
|
429 |
|
429 |
|