I don't think we need to enable the panic mode. This problem only
happens on a *very* limited number of scenarios, basically when the
BTL return a fragment in several iovecs. Few BTLs have this
capability, and even if they have it most of the time they prefer to
avoid it. Moreover, we never
On May 27, 2009, at 12:38 PM, George Bosilca wrote:
Depend on how we evaluate the fact that we can deliver wrong (and
truncated) data. From my perspective it is a blocker, and reflected
this on the CMR.
Correctness, schmorectness... who cares?
;-)
What I meant was: do we need to alert user
Depend on how we evaluate the fact that we can deliver wrong (and
truncated) data. From my perspective it is a blocker, and reflected
this on the CMR.
george.
On May 27, 2009, at 12:29 , Jeff Squyres wrote:
Never mind, I see CMR #1934.
Is this a critical update?
On May 27, 2009, at 12
Never mind, I see CMR #1934.
Is this a critical update?
On May 27, 2009, at 12:29 PM, Jeff Squyres wrote:
Does this need to go to v1.3?
On May 27, 2009, at 12:12 PM, wrote:
Author: bosilca
Date: 2009-05-27 12:12:18 EDT (Wed, 27 May 2009)
New Revision: 21300
URL: https://svn.open-mpi.org/
Does this need to go to v1.3?
On May 27, 2009, at 12:12 PM, wrote:
Author: bosilca
Date: 2009-05-27 12:12:18 EDT (Wed, 27 May 2009)
New Revision: 21300
URL: https://svn.open-mpi.org/trac/ompi/changeset/21300
Log:
Don't add the offset to all segments, only the first one should be
affected.
