From: Keith Packard <keithp@keithp.com>
To: Jason Cooper <jason@lakedaemon.net>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwrng: core - Allow for multiple simultaneous active hwrng devices
Date: Tue, 09 Aug 2016 10:58:05 -0700 [thread overview]
Message-ID: <86y445rfiq.fsf@hiro.keithp.com> (raw)
In-Reply-To: <20160809165710.GC2013@io.lakedaemon.net>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
Jason Cooper <jason@lakedaemon.net> writes:
> Perhaps a /dev/hwrng[0-9] per rng? That would lend itself nicely to a
> sysfs interface for per device quality, rate, and enabled attributes.
> e.g. /sys/class/hw_random/hwrng0/{device/,quality,rate,enabled}
I was interested in the data being provided for /dev/random; that seems
like the most important interface to me. But, exposing all of the
devices using consistent names does seem like a useful idea at some
level.
> /dev/hwrng could pull from the one with the highest quality, or user
> specified for backwards compatibility.
I like the notion of using all of them in turn; if one of them turns out
to be broken, you're still stirring in data from the others. After all,
the quality metric is provided by the device, we aren't doing any
analysis on the data to determine it independently.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 810 bytes --]
next prev parent reply other threads:[~2016-08-09 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 20:07 [PATCH] hwrng: core - Allow for multiple simultaneous active hwrng devices Keith Packard
2016-08-09 9:50 ` Herbert Xu
2016-08-09 16:57 ` Jason Cooper
2016-08-09 17:58 ` Keith Packard [this message]
2016-08-09 18:26 ` Jason Cooper
2016-08-09 19:01 ` Keith Packard
2016-08-09 20:18 ` Henrique de Moraes Holschuh
2016-08-09 23:26 ` Keith Packard
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=86y445rfiq.fsf@hiro.keithp.com \
--to=keithp@keithp.com \
--cc=herbert@gondor.apana.org.au \
--cc=jason@lakedaemon.net \
--cc=linux-crypto@vger.kernel.org \
--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