From: Eric Biggers <ebiggers@kernel.org>
To: Arno Wagner <arno@wagner.name>
Cc: dm-crypt@saout.de, John Lee McMahon <john.lee.mcmahon@gmail.com>
Subject: Re: [dm-crypt] Encryption speed and reversing the direction
Date: Tue, 25 Aug 2020 10:10:26 -0700 [thread overview]
Message-ID: <20200825171026.GA8389@sol.localdomain> (raw)
In-Reply-To: <20200825145929.GA2811@tansi.org>
On Tue, Aug 25, 2020 at 04:59:29PM +0200, Arno Wagner wrote:
> On Tue, Aug 25, 2020 at 04:44:50 CEST, Eric Biggers wrote:
> > On Tue, Aug 25, 2020 at 02:05:35AM -0400, John Lee McMahon wrote:
> [...]
> > Also if you actually care about random number generation performance, you
> > shouldn't be going through the kernel at all, except to read an initial
> > seed.
> [...]
>
> Not anymore. /dev/urandom has pretty good performance now.
> On my very old Phenom II fileserver, I get about 270MB/sec
> with a 5.x kernel.
Sure, just using /dev/urandom (or getrandom()) should be the first choice.
I was talking about the rare case where those still aren't fast enough.
- Eric
prev parent reply other threads:[~2020-08-25 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 6:05 [dm-crypt] Encryption speed and reversing the direction John Lee McMahon
2020-08-25 2:44 ` Eric Biggers
2020-08-25 14:59 ` Arno Wagner
2020-08-25 17:10 ` Eric Biggers [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=20200825171026.GA8389@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=arno@wagner.name \
--cc=dm-crypt@saout.de \
--cc=john.lee.mcmahon@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