public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lasse Kärkkäinen" <ljkarkk2@cc.hut.fi>
To: linux-kernel@vger.kernel.org
Subject: urandom is too slow
Date: Tue, 30 Oct 2012 16:55:22 +0200	[thread overview]
Message-ID: <508FEA5A.7010406@cc.hut.fi> (raw)

Apparently there has been little or no development on urandom even 
though the device is in widespread use for disk shredding and such use. 
The device emits data at rather slow rate of 19 MB/s even on modern 
hardware where other software-based PRNGs could do far better. An even 
better option seems to be utilizing AES for encrypting zeroes, using a 
random key, allowing for rates up to 500 MB/s with hardware that has 
AES-NI instructions.

Why is urandom so slow and why isn't AES hardware acceleration utilized?


             reply	other threads:[~2012-10-30 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 14:55 Lasse Kärkkäinen [this message]
2012-10-30 18:54 ` urandom is too slow Theodore Ts'o
2012-10-30 20:56   ` Pádraig Brady
2012-10-30 21:38   ` Alan Cox
2012-11-02  1:10     ` Lasse Kärkkäinen
2012-11-02 19:56       ` Theodore Ts'o

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=508FEA5A.7010406@cc.hut.fi \
    --to=ljkarkk2@cc.hut.fi \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox