unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludovic.courtes@inria.fr (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: 27850@debbugs.gnu.org
Subject: [bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple
Date: Mon, 31 Jul 2017 17:16:15 +0200	[thread overview]
Message-ID: <87379c4oxs.fsf@gnu.org> (raw)
In-Reply-To: <87wp6thqjc.fsf@i-ulialbion.it.manchester.ac.uk> (Dave Love's message of "Thu, 27 Jul 2017 16:01:59 +0100")

Hi Dave,

Dave Love <fx@gnu.org> skribis:

> The performance penalty for thread-multiple is supposed to be mitigated
> in the most recent openmpi, but not in this version, and most
> applications are happy with MPI_THREAD_FUNNELED.
>
>>From b860f75ed48c6d15e8f19b80ceede315df4db1fe Mon Sep 17 00:00:00 2001
> From: Dave Love <fx@gnu.org>
> Date: Thu, 27 Jul 2017 15:52:34 +0100
> Subject: [PATCH] gnu: mpi: openmpi: Don't enable thread-multiple. gnu: mpi:
>  openmpi-thread-multiple: Version with thread-multiple enabled.
>
> * gnu/packages/mpi.scm (openmpi): Don't enable thread-multiple.
> The support affects performance significantly.
> (openmpi-thread-multiple): New package.
> ---
>  gnu/packages/mpi.scm | 18 +++++++++++++++++-
>  1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/mpi.scm b/gnu/packages/mpi.scm
> index 54fdd35ad..678d7dd88 100644
> --- a/gnu/packages/mpi.scm
> +++ b/gnu/packages/mpi.scm
> @@ -130,10 +130,10 @@ bind processes, and much more.")
>      (native-inputs
>       `(("pkg-config" ,pkg-config)
>         ("perl" ,perl)))
> +    (outputs '("out" "lib" "debug"))

This should go to a separate patch.  Also please check the relative size
of each output and the “typical” closure size of openmpi users, to
motivate the need for a separate “lib” output (the “debug” output is
OK.)

I suspect some of the packages that depend on openmpi need to be changed
to have a dependency on both the “out” and the “lib” outputs, no?

>      (arguments
>       `(#:configure-flags `("--enable-static"
>  
> -                           "--enable-mpi-thread-multiple"

Should we upgrade our openmpi package instead of doing this?

> +    (description (string-append (package-description openmpi)
> +                                "\
> +
> +This version of openmpi has an implementation of MPI_Init_thread that provides
> +MPI_THREAD_MULTIPLE.  This won't work correctly with all transports (such as
> +openib), and the performance is generally worse than the vanilla openmpi
> +package, which only provides MPI_THREAD_FUNNELED."))))

Nitpick: we use literal strings in ‘description’ and ‘strings’ so that
they are picked up by xgettext for translation.

Thanks for looking into this!

Ludo’.

  reply	other threads:[~2017-07-31 15:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 15:01 [bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple Dave Love
2017-07-31 15:16 ` Ludovic Courtès [this message]
2017-07-31 18:09   ` Dave Love
2017-08-01  9:27     ` Ludovic Courtès
2017-08-01 16:06       ` Dave Love
2017-08-01 17:39         ` Ludovic Courtès
2017-08-01 20:10           ` Dave Love
2017-08-21 13:17             ` bug#27850: " Ludovic Courtès
2017-08-23 11:08               ` [bug#27850] " Dave Love
2017-08-23 21:34                 ` Ludovic Courtès
2017-09-01 10:35                   ` Dave Love
2017-09-01 22:10                     ` Ludovic Courtès
2017-09-07 16:16                       ` Dave Love

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87379c4oxs.fsf@gnu.org \
    --to=ludovic.courtes@inria.fr \
    --cc=27850@debbugs.gnu.org \
    --cc=fx@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).