There should be no datatype attached to the barrier, so it is normal you get
the zero values in the convertor.
Something weird is definitively going on. As there is no data to be sent, the
opal_convertor_set_position function is supposed to trigger the special path,
mark the convertor as comple
Indeed MPI_MAX_PORT_NAME is the right constant. A quick check indicate we're
using the right one, so feel free to remove this little piece of historic LAM
heritage.
george.
On Jun 15, 2012, at 00:00 , Jeff Squyres wrote:
> On Jun 14, 2012, at 3:53 PM, Ralph Castain wrote:
>
>> I believe we
(I'm catching up on email from an unanticipated absence - forgive the delay)
Pineapple did not hit a roadblock during the call. It is still on
track. I will start a separate thread for the discussion. As I have
said many (many, many) times, if the pineapple interface needs to
change for OMPI/ORTE/
Backing out r26597 solves my particular test cases. I'll back it out of
the trunk as well unless someone has objections.
I like how you say "same segfault." In certain cases, I just go on to
different segfaults. E.g.,
[2] btl_openib_handle_incoming(openib_btl, ep, frag, byte_len = 20U),
Seems like either a bug in the converter code or in setting up the send
request. r26597 ensures correctness in the case the btl's sendi does all three
of the following: returns an error, changes the converter, and returns a
descriptor.
Until we can find the root cause I pushed a change that pro
What: A Runtime Interposition Project - Codename Pineapple
Why: Define clear API and semantics for runtime requirements of the OMPI layer.
When:
- F June 22, 2012 - Work completed
- T June 26, 2012 - Discuss on teleconf
- R June 28, 2012 - Commit to trunk
Where: Trunk (development BitBucket b
On Jun 15, 2012, at 20:59 , Nathan Hjelm wrote:
> Seems like either a bug in the converter code or in setting up the send
> request. r26597 ensures correctness in the case the btl's sendi does all
> three of the following: returns an error, changes the converter, and returns
> a descriptor.
No
On 6/15/2012 11:59 AM, Nathan Hjelm wrote:
Until we can find the root cause I pushed a change that protects the reset by
checking if size> 0.
Let me know if that works for you.
It does.
