Jeff Squyres wrote:
Just to follow up for the web archives -- we discussed this on the
teleconf yesterday and decided that the assert()'s were not the way to
go. Brian was going to hack up a quick check at the end of OB1
add_procs that checks each btl's eager_limit, etc. Terry would expand
t
Just to follow up for the web archives -- we discussed this on the
teleconf yesterday and decided that the assert()'s were not the way to
go. Brian was going to hack up a quick check at the end of OB1
add_procs that checks each btl's eager_limit, etc. Terry would expand
this to cover dr a
Another way to do this which I am not sure makes sense is to just add
sizeof(mca_pml_ob1_hdr_t) to the btl_eager_limit passed into by the
user. Thus the defining the limit to be specifically for the user data
and not the internal headers
which the user may not have any inkling about. However,
I was playing around with some really silly fragment sizes (sub 72
bytes) when I ran into some asserts in the btl_openib_sendi. I traced
the assert to be caused by mca_pml_ob1_send_request_start_btl()
calculating the true eager_limit with the following line:
size_t eager_limit = btl->btl_ea
