From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56635)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1dcZhM-0007xD-3a
	for guix-patches@gnu.org; Tue, 01 Aug 2017 12:07:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1dcZhF-000671-VP
	for guix-patches@gnu.org; Tue, 01 Aug 2017 12:07:08 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:34471)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1dcZhF-00066n-SN
	for guix-patches@gnu.org; Tue, 01 Aug 2017 12:07:01 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1dcZhF-0004ba-Io
	for guix-patches@gnu.org; Tue, 01 Aug 2017 12:07:01 -0400
Subject: [bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple
Resent-Message-ID: <handler.27850.B27850.150160357817648@debbugs.gnu.org>
From: Dave Love <fx@gnu.org>
References: <87wp6thqjc.fsf@i-ulialbion.it.manchester.ac.uk>
	<87379c4oxs.fsf@gnu.org>
	<87o9s0bhro.fsf@i-ulialbion.it.manchester.ac.uk>
	<87lgn3skmm.fsf@inria.fr>
Date: Tue, 01 Aug 2017 17:06:11 +0100
In-Reply-To: <87lgn3skmm.fsf@inria.fr> ("Ludovic
	\=\?iso-8859-1\?Q\?Court\=E8s\?\=
	\=\?iso-8859-1\?Q\?\=22's\?\= message of "Tue, 1
	Aug 2017 11:27:45 +0200")
Message-ID: <87tw1r9sss.fsf@i-ulialbion.it.manchester.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <guix-patches.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-patches/>
List-Post: <mailto:guix-patches@gnu.org>
List-Help: <mailto:guix-patches-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=subscribe>
Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org
Sender: "Guix-patches" <guix-patches-bounces+kyle=kyleam.com@gnu.org>
To: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludovic.courtes@inria.fr>
Cc: 27850@debbugs.gnu.org

Ludovic Court=C3=A8s <ludovic.courtes@inria.fr> writes:

> Dave Love <fx@gnu.org> skribis:
>
>> Ludovic Court=C3=A8s <ludovic.courtes@inria.fr> writes:
>
> [...]
>
>>>>      (arguments
>>>>       `(#:configure-flags `("--enable-static"
>>>>=20=20
>>>> -                           "--enable-mpi-thread-multiple"
>>>
>>> Should we upgrade our openmpi package instead of doing this?
>>
>> I don't know whether they've fixed all the breakage I knew about in
>> OMPI 2 or whether there's still any penalty from thread-multiple.  1.10
>> seems fairly safe, but I don't have strong opinions if people think 2 is
>> solid.  Apart from ABI incompatibility, I assume it has the usual
>> incompatibilities at the mpirun/MCA level, and that they aren't well
>> documented.
>
> ABI compatibility is normally not an issue with Guix, so I=E2=80=99d be i=
n favor
> of upgrading to 2.0.3.  Would you like to do it?

Maybe, but what about the non-ABI compatibility I expect there is?  (I
don't know whether there's still any penalty from thread-multiple
anyhow; I guess not, as I see it's not the default.)  2.1 probably also
needs non-trivial work in figuring out whether it still needs a bundled
libevent, for instance.

If anyone's using it seriously, I'd have thought effort would be better
spent on support for SLURM (as it's in Guix) and supporting
high-performance fabrics (which I started on).