linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Sandy Harris <sandyinchina@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-crypto@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
	John Denker <jsd@av8n.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Stephan Mueller <smueller@chronox.de>
Subject: Re: random(4) changes
Date: Mon, 25 Apr 2016 21:00:58 -0400	[thread overview]
Message-ID: <20160426010058.GB28496@thunk.org> (raw)
In-Reply-To: <87twipn05w.fsf@tassilo.jf.intel.com>

On Mon, Apr 25, 2016 at 09:06:03AM -0700, Andi Kleen wrote:
> Sandy Harris <sandyinchina@gmail.com> writes:
> 
> There is also the third problem of horrible scalability of /dev/random
> output on larger systems, for which patches are getting ignored.
> 
> https://lkml.org/lkml/2016/2/10/716
> 
> Ignoring problems does not make them go away.

Sorry, too much travel, deadlines and conference this spring.  I
haven't forgot them.

						- Ted

  parent reply	other threads:[~2016-04-26  1:01 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 22:27 random(4) changes Sandy Harris
2016-04-23  7:52 ` Stephan Mueller
2016-04-24  2:03 ` Theodore Ts'o
2016-04-24  8:03   ` Stephan Mueller
2016-04-26  3:07     ` Theodore Ts'o
2016-04-26 11:04       ` Herbert Xu
2016-04-26 20:47         ` Andi Kleen
2016-04-27  4:23           ` Herbert Xu
2016-04-26 18:24       ` Stephan Mueller
2016-04-26 18:44       ` Pavel Machek
2016-04-26 18:55         ` Stephan Mueller
2016-04-26 19:41           ` Pavel Machek
2016-04-25 16:06 ` Andi Kleen
2016-04-25 17:25   ` Stephan Mueller
2016-04-25 17:38     ` Andi Kleen
2016-04-25 17:56       ` Stephan Mueller
2016-04-25 19:35         ` Andi Kleen
2016-04-26 12:01           ` Stephan Mueller
2016-04-27 17:47           ` Stephan Mueller
2016-04-26  1:00   ` Theodore Ts'o [this message]
2016-04-26 12:42   ` Sandy Harris
  -- strict thread matches above, loose matches on Subject: below --
2016-04-26  1:59 George Spelvin
2016-04-26 18:43 ` Stephan Mueller
2016-04-26 20:43   ` George Spelvin
2016-04-26 21:01     ` Stephan Mueller
2016-04-27  0:23       ` George Spelvin
2016-04-27 18:03         ` George Spelvin
2016-04-28 20:15         ` Stephan Mueller
2016-04-29  7:29           ` George Spelvin
2016-04-29  8:02             ` Stephan Mueller
2016-04-29  9:34               ` George Spelvin
2016-04-29  9:53                 ` Stephan Mueller
2016-04-29 11:04                   ` George Spelvin
2016-04-29 11:18                     ` Stephan Mueller
2016-04-29 18:02                       ` George Spelvin
2016-04-29 18:41                         ` Stephan Mueller
2016-04-29 20:08                           ` George Spelvin
2016-04-29 21:54                             ` Stephan Mueller
2016-04-29 22:32                               ` George Spelvin
2016-04-29  0:47         ` George Spelvin

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=20160426010058.GB28496@thunk.org \
    --to=tytso@mit.edu \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=jason@lakedaemon.net \
    --cc=jsd@av8n.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandyinchina@gmail.com \
    --cc=smueller@chronox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).