From: "Theodore Ts'o" <tytso@mit.edu>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Jeff Epler <jepler@unpythonic.net>,
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: Fri, 25 Sep 2015 16:24:25 -0400 [thread overview]
Message-ID: <20150925202425.GA14209@thunk.org> (raw)
In-Reply-To: <56059B8A.2010402@gmail.com>
On Fri, Sep 25, 2015 at 03:07:54PM -0400, Austin S Hemmelgarn wrote:
>
> Interestingly, based on what dieharder is already saying about performance,
> /dev/urandom is slower than AES_OFB (at least, on this particular system,
> happy to provide hardware specs if someone wants).
Yeah, not surprised by that. We're currently using a crypto hash
instead of AES, which means we're not doing any kind of hardware
acceleration.
Crazy applications that want to spend 100% of the CPU generating
random numbers instead of you know, doing _useful_ work
notwithstanding, /dev/urandom never had high performance as one of its
design goals. The assumption was that if you needed that kind of
performance, you would use a user-space cryptographic random number
generator.
- Ted
next prev parent reply other threads:[~2015-09-25 20:24 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
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 [this message]
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=20150925202425.GA14209@thunk.org \
--to=tytso@mit.edu \
--cc=ahferroin7@gmail.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=herbert@gondor.apana.org.au \
--cc=jepler@unpythonic.net \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.