[Pvfs2-developers] Sanity check

[Sam Lang]

On Dec 12, 2006, at 12:55 PM, Scott Atchley wrote:

> Hi all,
>
> I just want to confirm that when sending to a new server, the order  
> of operations on the client is:
>
> BMI_meth_method_addr_lookup()	/* returns new method_addr_p */
> BMI_meth_post_recv() 		/* using the new method_addr_p */
> BMI_meth_post_sendunexpected()	/* using the new method_addr_p */
>
> Primarily, I want to confirm that BMI_meth_method_addr_lookup()  
> prior to both the recv and the sendunexpected.

Yes, that's correct.

>
> On the server, I wait for new connection messages, then I create a  
> new method_addr_p and register it using bmi_method_addr_reg_callback 
> () as well as my own connection management structure. I then send  
> my own ack to the client, which allows it to start sending messages.

You're talking about the initial handshake that mx is going to do,  
right?  I think as long as you call the reg_callback, everything else  
is up to you.

 From outside the bmi interface, the first BMI call made (besides the  
context init stuff), is to BMI_testunexpected.  I'm not sure that  
answers (or that I understand) your question on the server side though.

-sam
>
> Thanks,
>
> Scott
> _______________________________________________
> Pvfs2-developers mailing list
> Pvfs2-developers at beowulf-underground.org
> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
>