From: Jeff Epler <jepler@unpythonic.net>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, kirill.shutemov@linux.intel.com,
herbert@gondor.apana.org.au, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/3] Make /dev/urandom scalable
Date: Thu, 24 Sep 2015 15:00:32 -0500 [thread overview]
Message-ID: <20150924200032.GB2835@unpythonic.net> (raw)
In-Reply-To: <56044ADB.5050102@gmail.com>
On Thu, Sep 24, 2015 at 03:11:23PM -0400, Austin S Hemmelgarn wrote:
> I will make a point however to run some tests over the weekend on a
> current kernel version (4.2.1), with the current dieharder version I
> have available (3.31.1).
Please report your findings. If urandom is worse than AES_OFB in
statistical tests, we need to know about it.
I'm an hour into some test-to-failure runs of diehard_count_1s_str on
various RNGs -- urandom, AES_OFB, mt19937_1999, and rand48. So far at
psamples >=29000 none have failed, so there's no result to report. (test
8 was chosen by mere human pseudorandomness; hey, it finds in <2s that
RANDU is a flawed generator)
dieharder -d 8 -g 205 -Y 2 -k 2
dieharder -d 8 -g 200 -Y 2 -k 2
dieharder -d 8 -g 14 -Y 2 -k 2
dieharder -d 8 -g 22 -Y 2 -k 2
If the results are other than "both urandom and aes_ofb were running
when I had to reboot my laptop", I'll report my results as well.
Jeff
next prev parent reply other threads:[~2015-09-24 20:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 23:16 [PATCH 1/3] Make /dev/urandom scalable Andi Kleen
2015-09-22 23:16 ` [PATCH 2/3] random: Make input to output pool balancing per cpu Andi Kleen
2015-09-22 23:16 ` [PATCH 3/3] random: Add pool name to urandom_read trace point Andi Kleen
2015-09-22 23:25 ` [PATCH 1/3] Make /dev/urandom scalable Andi Kleen
2015-09-23 10:32 ` Rasmus Villemoes
2015-09-23 21:54 ` Andi Kleen
2015-09-23 19:40 ` Austin S Hemmelgarn
2015-09-23 23:28 ` Andi Kleen
2015-09-24 11:37 ` Austin S Hemmelgarn
2015-09-24 13:12 ` Theodore Ts'o
2015-09-24 16:00 ` Austin S Hemmelgarn
2015-09-24 16:52 ` Jeff Epler
2015-09-24 19:11 ` Austin S Hemmelgarn
2015-09-24 20:00 ` Jeff Epler [this message]
2015-09-24 20:14 ` Theodore Ts'o
2015-09-25 11:41 ` Austin S Hemmelgarn
2015-09-25 19:07 ` Austin S Hemmelgarn
2015-09-25 20:24 ` Theodore Ts'o
2015-09-29 12:06 ` Austin S Hemmelgarn
2015-09-29 11:57 ` Austin S Hemmelgarn
2015-09-23 21:10 ` Theodore Ts'o
2015-09-23 21:25 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2015-09-24 17:19 Updated scalable urandom patchkit Andi Kleen
2015-09-24 17:19 ` [PATCH 1/3] Make /dev/urandom scalable Andi Kleen
2015-09-30 14:40 ` Rasmus Villemoes
2015-10-06 22:05 Andi Kleen
2016-02-10 23:01 Scalable random patchkit revisited Andi Kleen
2016-02-10 23:01 ` [PATCH 1/3] Make /dev/urandom scalable Andi Kleen
2016-03-01 5:17 Andi Kleen
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=20150924200032.GB2835@unpythonic.net \
--to=jepler@unpythonic.net \
--cc=ahferroin7@gmail.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=herbert@gondor.apana.org.au \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 NNTP newsgroup(s).