public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	sneves@dei.uc.pt
Subject: Re: [PATCH] random: use rejection sampling for uniform bounded random integers
Date: Mon, 17 Oct 2022 23:31:03 -0600	[thread overview]
Message-ID: <Y046F2pGjC0apna0@zx2c4.com> (raw)
In-Reply-To: <Y02ehdiCtHyLErB8@sol.localdomain>

On Mon, Oct 17, 2022 at 11:27:17AM -0700, Eric Biggers wrote:
> On Sun, Oct 16, 2022 at 08:37:53PM -0600, Jason A. Donenfeld wrote:
> > In order to be efficient, we implement a kernel-specific variant of
> > Daniel Lemire's algorithm from "Fast Random Integer Generation in an
> > Interval", linked below. The kernel's variant takes advantage of
> > constant folding to avoid divisions entirely in the vast majority of
> > cases, works on both 32-bit and 64-bit architectures, and requests a
> > minimal amount of bytes from the RNG.
> > 
> > Link: https://arxiv.org/pdf/1805.10941.pdf
> 
> Thanks for doing this!  Your code looks correct, but it was hard for me to
> understand until I read the paper that is linked to.  Could you include a brief
> comment in the code that explains the algorithm?  Also, though the code looks
> correct, I assume that you've also explicitly tested that each of the four code
> paths produce uniform random numbers as intended?

Yes, I've tested those, and they work. (Threw a lot of cores and ram at
it.)

I could include a comment, sure. What do you have in mind? A
line-by-line thing, or just a short blurb at the top of the function?

Jason

  parent reply	other threads:[~2022-10-18  5:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  2:37 [PATCH] random: use rejection sampling for uniform bounded random integers Jason A. Donenfeld
2022-10-17 18:27 ` Eric Biggers
2022-10-17 20:39   ` Yann Droneaud
2022-10-18  5:31   ` Jason A. Donenfeld [this message]
2022-10-18  7:04     ` Eric Biggers
2022-10-18 17:34       ` [PATCH v2] " Jason A. Donenfeld

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=Y046F2pGjC0apna0@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=ebiggers@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sneves@dei.uc.pt \
    /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