Hal Rosenstock wrote:
Hi Arlin,
On Fri, 2005-07-15 at 13:04, Arlin Davis wrote:
Your implementation is fine, as long as the correct return values are used
and the sync version works. I currently get returned a 1 but the ib_route
data is not filled in and the req_id == 0. I would expect a 0 returned
and a
valid req_id if the ib_route cannot be processed.
for ret = ib_at_route_by_ip( async_cb provided ), I read this as:
if ret > 0 then ib_route output data is written, resolve complete
if ret == 0 then req_id is written with valid id to cancel or poll
if ret < 0 error
Am I reading this right?
Try this patch and let me know if this works for you.
Thanks.
-- Hal
Hal,
Yes, it returns the route data (GID) when the return == 1. However, I
still get a callback event with a req_id ==0 which is somewhat
unexpected. This seems unnecessary given that ib_at_route_by_ip() just
returned the data. Is this the expected behavior?
Here is my output from the call and from the at_thread.
4116 Running as client
4116 Server Name: iclust-20-ib0
4116 Server Net Address: 192.168.0.20
dapl_ep_connect (0x515c40, {4294967232.4294967208.0.20}, 115D3, 5000000,
0, (nil), 0, 0)
connect: r_SID 71123, pdata (nil), plen 0
connect: at_route ret=1, req_id 0, GID fe80000000000000
0002c90200004071 <<<< ib_route info returned with call
dapl_ep_connect () returns 0x0
4116 Waiting for connect response
at_thread: get_callback
rt_comp_handler: conn 0x519e30, req_id 0 rec_num 1
rt_comp_handler: SRC GID subnet fe80000000000000 id 0002c9020000409d
<<< get_callback event fires
rt_comp_handler: DST GID subnet fe80000000000000 id 0002c90200004071
at_thread: callback woke
-arlin
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
