From: Brian Gough <bjg@network-theory.co.uk>
To: GSL Discussion list <gsl-discuss@sources.redhat.com>
Subject: Re: 64 bit rng interface?
Date: Mon, 17 Mar 2008 23:20:00 -0000 [thread overview]
Message-ID: <87r6e9x7jd.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0803171008180.7337@cain.rgb.private.net>
At Mon, 17 Mar 2008 10:27:57 -0400 (EDT),
Robert G. Brown wrote:
> a) Are there plans for a 64-bit GSL RNG interface? A number of my
> correspondants are working on algorithms that can run equally well at 64
> bits, and 64 bit unsigned ints invert to double precision uniform
> deviates.
Is it possible to do it using the existing interface in some way? If
it would need a duplicate 64-bit interface it's not really feasible.
> b) Are there plans for a "vectorized" interface? I'd envision this
> as a user-selectable switch on the creation/initialization step that
> builds (say) a page-sized buffer. On the first call, this buffer would
> be filled with random bits in a single step, keeping the generation code
> on the CPU and cache and permitting certain pipelining optimizations.
> Subsequent calls would simply walk a pointer through the buffer to the
> end, where the "refill buffer" command would once again be called and
> the pointer reset to the beginning before returning.
The possibility is there to do that, or to provide a gsl_rng_get_array
function. If there is a realistic benchmark that shows a large
performance improvement (>2x) then that would be a good motivation.
Currently it seems like motivation is the missing ingredient.
--
Brian Gough
prev parent reply other threads:[~2008-03-17 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 14:31 Robert G. Brown
2008-03-17 23:20 ` Brian Gough [this message]
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=87r6e9x7jd.wl%bjg@network-theory.co.uk \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.redhat.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).