On Dec 11, 2013, at 5:33 PM, "Prindeville, Philip"
wrote:
> I was wondering what the current state of iWARP development is.
Open MPI's iWARP support is part of the "openib" BTL (so named because
OpenFabrics used to be known as OpenIB, before iWARP joined, and we never
changed the name of ou
Don’t look in the 1.7.3 for SCTP. Instead, take a look at the trunk where we
still have the SCTP BTL (ompi/mca/btl/sctp).
George.
On Dec 11, 2013, at 17:33 , Prindeville, Philip
wrote:
> Hi.
>
> I was wondering what the current state of iWARP development is. There are
> some features w
Hi.
I was wondering what the current state of iWARP development is. There are some
features we're interested in, and from what I can tell the iWARP RFCs/Internet
Drafts haven't caught up to related developments. Part of our interest is in
using SCTP as the LLP for iWARP, and updating that ada
Can you send the opal_config.h file from your build tree?
This will help us look into what's going on.
On Dec 10, 2013, at 8:53 AM, Philipp Thomas wrote:
> Two of the asm tests are failing on my machine with
> Intel(R) Core(TM) i7-4960X CPU @ 3.60GHz running openSUSE 13.1 and
> gcc (SUSE Linu
Hi,
Open MPI's signal handler (show_stackframe function defined in
opal/util/stacktrace.c) calls non-async-signal-safe functions
and it causes a problem.
See attached mpisigabrt.c. Passing corrupted memory to realloc(3)
will cause SIGABRT and show_stackframe function will be invoked.
But invoked
