On Dec 12, 2013, at 4:31 PM, "Prindeville, Philip"
wrote:
> I think I understand.
>
> I’ll pull a copy of trunk and dig around in there.
>
> Is there a reason that the code can’t be gated by conditional compilation
> flags or detect the environment at run-time?
I'm not sure what you're ask
rom:* devel [mailto:devel-boun...@open-mpi.org] *On Behalf Of *Ralph
> Castain
> *Sent:* Thursday, December 12, 2013 8:41 AM
> *To:* Open MPI Developers
>
> *Subject:* Re: [OMPI devel] iWARP development
>
>
>
> Be aware that we removed SCTP from the 1.7 release series beca
nce of the SCTP code that's in trunk?
Thanks,
-Philip
From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain
Sent: Thursday, December 12, 2013 8:41 AM
To: Open MPI Developers
Subject: Re: [OMPI devel] iWARP development
Be aware that we removed SCTP from the 1.7 release s
Be aware that we removed SCTP from the 1.7 release series because of its
unknown state of repair - I don't believe anyone has tested it in quite
some time, and nobody has been maintaining it so far as we know. Not saying
it won't work - just saying that I don't think we know :-/
On Wed, Dec 11,
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
