On Jul 23, 2009, at 12:06 , Brian W. Barrett wrote:
On Thu, 23 Jul 2009, Jeff Squyres wrote:
There are two solutions I can think of. Which should we do?
a. Pass the (max?) PML header size down into the BTL during
initialization such that the the btl_XXX_eager_limit can
represent the max MPI
On Thu, 23 Jul 2009, Jeff Squyres wrote:
There are two solutions I can think of. Which should we do?
a. Pass the (max?) PML header size down into the BTL during
initialization such that the the btl_XXX_eager_limit can
represent the max MPI data payload size (i.e., the BTL can siz
WHAT: a) Clarify the actual max MPI payload size for eager messages
(i.e., the exact meaning of btl_XXX_eager_limit), and b) allow
network administrators to shape network traffic by publishing
actual BTL max wire fragment sizes (i.e., MPI max payload size +
max PML header s
