George,
Were you suggesting that the proposed new parameter
"max_rdma_single_rget" be set by the individual btls similar to
"btl_eager_limit"? Seems to me to that is the better approach if I am
to move forward with this.
-DON
On 10/06/09 11:14, Don Kerr wrote:
I agree there is probably a l
Don,
The problem is that a particular BTL doesn't have the knowledge about
the other selected BTL, so allowing the BTLs to set this limit is not
as easy as it sound. However, in the case two identical BTLs are
selected and that they are the only ones, this clearly is a better
approach.
Jeff,
I'm intrigued by this commit. Here is how I read the patch:
1. In most of the cases you added one opal_output on top of the
already existing orte_show_help
2. In some other cases you replaced meaningful messages such as
"mca_common_sm_mmap_init: orte_rml.recv failed from %d with
Thanks for the sanity check.
I don't know what I was thinking for the first 2 -- those are clearly
extraneous. The 3rd one, I meant to remove the opal_output() and have
it just be the ORTE_ERROR_LOG (the existing opal_output() doesn't
really tell much extra).
I'll fix.
On Oct 7, 2009,
