mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add_mouse_randomness
Date: Fri, 5 Sep 2003 12:05:29 -0500	[thread overview]
Message-ID: <20030905170529.GM31897@waste.org> (raw)
In-Reply-To: <UTC200309050916.h859G5813732.aeb@smtp.cwi.nl>

On Fri, Sep 05, 2003 at 11:16:05AM +0200, Andries.Brouwer@cwi.nl wrote:
>     From oxymoron@waste.org  Fri Sep  5 07:01:30 2003
>     From: Matt Mackall <mpm@selenic.com>
> 
>     > Today:
>     > Every keypress and every key release causes two calls of
>     > add_mouse_randomness and one call of add_keyboard_randomness.
>     > Key repeat causes lots of calls of add_mouse_randomness.
>     > 
>     > The random driver contains a mechanism (delta, delta2, delta3)
>     > for estimating the amount of entropy in a stream of moments in
>     > time. But the fact that every event causes two calls, very
>     > quickly after each other, poisons this mechanism, and makes us
>     > overestimate.
> 
>     The real problem is that the deltas are calculated from gigahertz
>     cycle counters, but yes, we're calling too frequently and blowing away
>     useful history. I've experimented with making the deltas per-source as
>     well.
> 
> I wouldnt know what is wrong with using gigahertz cycle counters.
> The deltas are already per-source.

Actually, they're only per-class. So if you have multiple mice,
keyboards, drives, etc., they interfere with each other's deltas and
increase the entropy estimates overall.

-- 
Matt Mackall : http://www.selenic.com : of or relating to the moon

  reply	other threads:[~2003-09-05 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-05  9:16 Andries.Brouwer
2003-09-05 17:05 ` Matt Mackall [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-04 22:51 Andries.Brouwer
2003-09-05  3:21 ` Matt Mackall

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=20030905170529.GM31897@waste.org \
    --to=mpm@selenic.com \
    --cc=Andries.Brouwer@cwi.nl \
    --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

all inboxes | Powered by JetHome®