From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: guix-devel@gnu.org
Subject: Re: Guix on clusters and in HPC
Date: Thu, 20 Oct 2016 16:17:09 +0200 [thread overview]
Message-ID: <87lgxj9kbe.fsf@gnu.org> (raw)
In-Reply-To: <20161019.091750.442073013177424288.post@thomasdanckaert.be> (Thomas Danckaert's message of "Wed, 19 Oct 2016 09:17:50 +0200 (CEST)")
Thomas Danckaert <post@thomasdanckaert.be> skribis:
> From: ludo@gnu.org (Ludovic Courtès)
> Subject: Guix on clusters and in HPC
> Date: Tue, 18 Oct 2016 16:20:43 +0200
>
>> So I’ve come up with an initial list of work items going from the
>> immediate needs to crazy ideas (batch scheduler integration!) that
>> hopefully make sense to cluster/HPC people. I’d be happy to get
>> feedback, suggestions, etc. from whoever is interested!
>
> Here's a semi-crazy suggestion: some HPC people really like the intel
> compiler/math kernel library, so a way to switch toolchains on
> packages, and somehow integrate “foreign” toolchains would suit
> them. But that might be “advocating the use of non-free software” (in
> fact I almost feel like a heretic for bringing this up :-) ...).
Yeah, I’m aware of this. In section 5 of
<https://hal.inria.fr/hal-01161771/en>, we wrote:
GNU Guix does not provide proprietary software packages.
Unfortunately, proprietary software is still relatively common in HPC,
be it linear algebra libraries or GPU support. Yet, we see it as a
strength more than a limitation. Often, these “black boxes”
inherently limit reproducibility—how is one going to reproduce a
software environment without permission to run the software in the
first place? What if the software depends on the ability to “call
home” to function at all? More importantly, we view reproducible
software environments and reproducible science as a tool towards
improved and shared knowledge; developers who deny the freedom to
study and modify their code work against this goal.
As heretic as it may seem in HPC circles ;-), I stand by this.
Regarding GPU support, there’s light on the horizon with GCC’s new PTX
backend, OpenACC support, and with libgomp’s offloading support.
We’ll see!
Ludo’.
next prev parent reply other threads:[~2016-10-20 14:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 14:20 Guix on clusters and in HPC Ludovic Courtès
2016-10-18 14:55 ` Christopher Allan Webber
2016-10-18 16:04 ` Ludovic Courtès
2016-10-18 16:47 ` Roel Janssen
2016-10-19 11:11 ` Ricardo Wurmus
2016-10-21 12:11 ` Roel Janssen
2016-10-20 14:08 ` Ludovic Courtès
2016-10-21 9:32 ` Ricardo Wurmus
2016-10-26 11:51 ` Ludovic Courtès
2016-11-01 23:25 ` Ben Woodcroft
2016-11-02 16:03 ` Pjotr Prins
2016-11-04 22:05 ` Pjotr Prins
2016-11-05 2:17 ` Chris Marusich
2016-11-05 16:15 ` Roel Janssen
2016-11-08 12:39 ` Ludovic Courtès
2016-11-03 13:47 ` Ludovic Courtès
2016-10-19 7:17 ` Thomas Danckaert
2016-10-20 14:17 ` Ludovic Courtès [this message]
2016-10-25 2:56 ` myglc2
2016-10-26 12:00 ` Ludovic Courtès
2016-11-01 0:11 ` myglc2
2016-10-26 12:08 ` Ricardo Wurmus
2016-10-31 22:01 ` myglc2
2016-11-01 7:15 ` Ricardo Wurmus
2016-11-01 12:03 ` Ben Woodcroft
2016-11-03 13:44 ` Ludovic Courtès
2016-11-19 6:18 ` Ben Woodcroft
2016-11-21 14:07 ` Ludovic Courtès
2016-10-26 15:43 ` Eric Bavier
2016-10-26 16:31 ` Ludovic Courtès
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=87lgxj9kbe.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=post@thomasdanckaert.be \
/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).