From: "Andrew W. Steiner" <awsteiner@gmail.com>
To: "Jochen Küpper" <kuepper.jochen@googlemail.com>
Cc: "GSL Discuss Mailing List" <gsl-discuss@sourceware.org>
Subject: Re: OpenMP GSL
Date: Mon, 14 Apr 2008 19:09:00 -0000 [thread overview]
Message-ID: <63c059b10804141208u7b59b4camdc322ec10c97141d@mail.gmail.com> (raw)
In-Reply-To: <5644665F-AAC2-469C-920D-6B13DBE87085@googlemail.com>
Exciting thought, but I'd lean towards a separate package. In any case
"parallelization of GSL" is kind of a loaded term. It's not clear to
me that many of the routines presented in GSL are easily
"parallelizable" per se?
On Mon, Apr 14, 2008 at 2:46 PM, Jochen Küpper
<kuepper.jochen@googlemail.com> wrote:
> Hi,
>
> I was wondering whether there are any plans for the parallelization of GSL?
>
> For example, I found this article on "Parallelization of GSL: Architecture,
> Interfaces, and Programming Models" form 2004:
>
> https://commerce.metapress.com/content/jtp50vjc1e3gwane/resource-secured/?target=fulltext.pdf&sid=medqeqrui2yyng45okahx345&sh=www.springerlink.com
>
> I also found a message by Brian Gough from 2002 stating that it would not
> fit the design of GSL (Message-ID: <15656.48877.30970.694792@debian>).
>
> Would there be any objections if one started to a few include OpenMP
> directives in the code? They would not at all interfere with normal usage of
> GSL in single-threaded calculations. If they should even be optional for the
> use of GSL in OpenMP calculations, they could be flagged by a run-time or
> compile-time (preferred for performance) switch.
>
> Thoughts?
>
> Greetings,
> Jochen
> --
> Einigkeit und Recht und Freiheit
> http://www.Jochen-Kuepper.de
> Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D
> Sex, drugs and rock-n-roll
>
>
>
next prev parent reply other threads:[~2008-04-14 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 18:46 Jochen Küpper
2008-04-14 19:09 ` Andrew W. Steiner [this message]
2008-04-15 8:54 ` Brian Gough
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63c059b10804141208u7b59b4camdc322ec10c97141d@mail.gmail.com \
--to=awsteiner@gmail.com \
--cc=gsl-discuss@sourceware.org \
--cc=kuepper.jochen@googlemail.com \
/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.
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).