One thing I noticed: For an unexpected receive, we do a peek on the socket (recv(...MSG_PEEK)) and see if a full bmi header is there. If it is, we set the socket back to blocking mode, do a blocking recv for the header, and set then set the socket back to non-blocking mode. Rob pointed out that we probably don't need to set the socket to blocking. Is there some reason we do that, instead of just do the recv in non-blocking mode since we've already checked that the bytes are there?
Yeah, I think you are right about this- nbrecv should be just fine for this case.
Thanks for putting all of those graphs together. Very interesting, but so far I have no clue why that would happen.
-Phil _______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
