From: Deepak Saxena <dsaxena@plexity.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] RNG rewrite...
Date: Mon, 17 Oct 2005 18:00:28 -0700 [thread overview]
Message-ID: <20051018010028.GA16005@plexity.net> (raw)
In-Reply-To: <43543455.4080206@pobox.com>
On Oct 17 2005, at 19:31, Jeff Garzik was caught saying:
> >PCI devices, but I don't know enough about x86 to say whether msr
> >instructions can execute out of userspace (or if we want them to...).
>
> All of the hot path RNG stuff can and should be moved to userspace.
>
> Right now the path is
>
> kernel /dev/hwrandom -> rngd -> add /dev/random entropy
>
> All three current vendors shown in hw_random.c are doable in userspace.
> Intel uses MMIO, AMD uses PIO, and VIA uses a specialized CPU
> instruction. As HPA mentioned, you can use the MSR driver for control.
>
> Patches welcome! http://sf.net/projects/gkernel/
OK...I already did most of a rewrite keeping the driver in user space
and added support for IXP4xx and OMAP but will look at the msr driver.
However, looking at the MPC85xx and the Alchemy MIPs parts with RNGs,
they have interrupt sources for error conditions so those need to be
in kernel...
~Deepak
--
Deepak Saxena - dsaxena@plexity.net - http://www.plexity.net
When law and duty are one, united by religion, you never become fully
conscious, fully aware of yourself. You are always a little less than
an individual. - Frank Herbert
next prev parent reply other threads:[~2005-10-18 0:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 4:31 [RFC] RNG rewrite Deepak Saxena
2005-10-15 10:40 ` Jeff Garzik
2005-10-16 0:53 ` Deepak Saxena
2005-10-17 23:15 ` H. Peter Anvin
2005-10-17 23:26 ` Jeff Garzik
2005-10-18 0:22 ` H. Peter Anvin
2005-10-17 23:31 ` Jeff Garzik
2005-10-18 1:00 ` Deepak Saxena [this message]
2005-10-18 1:05 ` Deepak Saxena
2005-10-18 1:09 ` Jeff Garzik
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=20051018010028.GA16005@plexity.net \
--to=dsaxena@plexity.net \
--cc=jgarzik@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox