public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Deepak Saxena <dsaxena@plexity.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.net, akpm@osdl.org,
	tony@atomide.com
Subject: Re: [patch 0/5] RNG cleanup & new drivers attempt #1
Date: Wed, 19 Oct 2005 10:25:33 -0700	[thread overview]
Message-ID: <20051019172532.GA13917@plexity.net> (raw)
In-Reply-To: <43565FB1.50301@pobox.com>

On Oct 19 2005, at 11:01, Jeff Garzik was caught saying:
> Not interesting in pursuing this path.  This has been discussed 
> endlessly, check the archives.
> 
> We want the FIPS tests.  Hardware (especially cheap hardware) is often 
> known to go haywire.  Trusting hardware to do the FIPS tests is pretty 
> silly, since you're trusting the piece that might go haywire to tell you 
> its OK.  RNGs have a history of suddenly providing non-random data, for 
> a variety of reasons (usually poor board wiring).
> 
> We also want the userspace daemon because that gives the sysadmin far 
> more control over how much entropy is added to the system.  99.9% of the 
> cases in the real world, we don't want the RNG pumping entropy into the 
> pool at full speed.  That will likely pump in more data than a system 
> needs, chewing CPU.  The admin can't even kill the daemon to reclaim his 
> CPU, if its all in-kernel.

OK, understood. But other than the fastpath idea, are you OK with 
the direction I took with the code?

~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

      reply	other threads:[~2005-10-19 17:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19  8:19 [patch 0/5] RNG cleanup & new drivers attempt #1 dsaxena
2005-10-19  8:19 ` [patch 1/5] Remove existing hw_random implementation dsaxena
2005-10-19  8:19 ` [patch 2/5] Core HW RNG support dsaxena
2005-10-24 10:45   ` Pavel Machek
2005-10-19  8:19 ` [patch 3/5] Intel IXP4xx driver dsaxena
2005-10-19  8:19 ` [patch 4/5] x86 driver dsaxena
2005-10-19  8:19 ` [patch 5/5] TI OMAP driver dsaxena
2005-10-19  9:36   ` Eric Piel
2005-10-19  9:44     ` Deepak Saxena
2005-10-21 16:35       ` Tony Lindgren
2005-10-21 18:00         ` Tony Lindgren
2005-10-21 19:10           ` Tony Lindgren
2005-10-23 18:12             ` Deepak Saxena
2005-10-19 15:01 ` [patch 0/5] RNG cleanup & new drivers attempt #1 Jeff Garzik
2005-10-19 17:25   ` Deepak Saxena [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=20051019172532.GA13917@plexity.net \
    --to=dsaxena@plexity.net \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=jgarzik@pobox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony@atomide.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