All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Sean Hunter <sean@dev.sportingbet.com>
Cc: Ken Brownfield <brownfld@irridia.com>,
	Tim Schmielau <tim@physik3.uni-rostock.de>,
	"Proescholdt, timo" <Timo.Proescholdt@brk-muenchen.de>,
	linux-kernel@vger.kernel.org
Subject: Re: randomness - compaq smart array driver
Date: Wed, 13 Feb 2002 10:49:24 -0500	[thread overview]
Message-ID: <3C6A8B04.D7141173@nortelnetworks.com> (raw)
In-Reply-To: <410B51F29EA8D3118EE400508B44AE2B3C6FB3@RZ_NT_MAIL> <Pine.LNX.4.33.0202111754560.5685-100000@gans.physik3.uni-rostock.de> <20020213071445.A20717@asooo.flowerfire.com> <20020213150850.H26054@dev.sportingbet.com>

Sean Hunter wrote:

> Randomness from network packet timings can be gathered entirely in userspace by
> using a packet socket.  I am busy writing an "additional entropy daemon" to
> gather entropy from this and other sources[1], clean it up, test its fitness,
> estimate its information content, and feed it into the random pool.  This job
> is (IMO) better done in userspace because there we can run fitness tests on the
> stream more easily because we have floating point etc.

However, if you're doing that, then you incur the cost of copying every incoming
packet and sending it up to userspace.  For a busy server, this could be
unacceptable.

Also, how are you timing the incoming packets?  In kernel space we can get
accuracy of a few tens of nanoseconds for timing the interrupts--how do you
approach this in userspace when your userspace process can be scheduled out?  

Even if we timestamp the packets with microsecond accuracy, we are still a few
orders of magnitude short of the accuracy attainable in the kernel, with
correspondingly less entropy that can be extracted.

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

  reply	other threads:[~2002-02-13 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-11 15:00 randomness - compaq smart array driver Proescholdt, timo
2002-02-11 16:58 ` Tim Schmielau
2002-02-13 13:14   ` Ken Brownfield
2002-02-13 15:08     ` Sean Hunter
2002-02-13 15:49       ` Chris Friesen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-11 17:41 Stephen Cameron

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=3C6A8B04.D7141173@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=Timo.Proescholdt@brk-muenchen.de \
    --cc=brownfld@irridia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean@dev.sportingbet.com \
    --cc=tim@physik3.uni-rostock.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.