From: Theodore Ts'o <tytso@mit.edu>
To: Oliver Mangold <o.mangold@gmail.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: Poor RNG performance on Ryzen
Date: Fri, 21 Jul 2017 10:47:42 -0400 [thread overview]
Message-ID: <20170721144741.4igkvsd2fowptsy2@thunk.org> (raw)
In-Reply-To: <09c9be2b-8b4d-ee06-8071-4f748fdb5970@gmail.com>
On Fri, Jul 21, 2017 at 01:39:13PM +0200, Oliver Mangold wrote:
> Better, but obviously there is still much room for improvement by reducing
> the number of calls to RDRAND.
Hmm, is there some way we can easily tell we are running on Ryzen? Or
do we believe this is going to be true for all AMD devices?
I guess we could add some kind of "has_crappy_arch_get_random()" call
which could be defined by arch/x86, and change how aggressively we use
arch_get_random_*() depending on whether has_crappy_arch_get_random()
returns true or not....
- Ted
next prev parent reply other threads:[~2017-07-21 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 7:12 Poor RNG performance on Ryzen Oliver Mangold
2017-07-21 9:26 ` Jan Glauber
2017-07-21 11:39 ` Oliver Mangold
2017-07-21 14:47 ` Theodore Ts'o [this message]
2017-07-21 14:55 ` Oliver Mangold
2017-07-22 18:16 ` Theodore Ts'o
2017-07-25 6:20 ` Jan Glauber
2017-07-21 15:04 ` Gary R Hook
2017-07-21 12:11 ` Jeffrey Walton
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=20170721144741.4igkvsd2fowptsy2@thunk.org \
--to=tytso@mit.edu \
--cc=linux-crypto@vger.kernel.org \
--cc=o.mangold@gmail.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