From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S933288AbbIYUYn (ORCPT <rfc822;w@1wt.eu>);
	Fri, 25 Sep 2015 16:24:43 -0400
Received: from imap.thunk.org ([74.207.234.97]:43574 "EHLO imap.thunk.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S933052AbbIYUYl (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 25 Sep 2015 16:24:41 -0400
Date: Fri, 25 Sep 2015 16:24:25 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Jeff Epler <jepler@unpythonic.net>, Andi Kleen <andi@firstfloor.org>,
        linux-kernel@vger.kernel.org, kirill.shutemov@linux.intel.com,
        herbert@gondor.apana.org.au, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/3] Make /dev/urandom scalable
Message-ID: <20150925202425.GA14209@thunk.org>
Mail-Followup-To: Theodore Ts'o <tytso@mit.edu>,
	Austin S Hemmelgarn <ahferroin7@gmail.com>,
	Jeff Epler <jepler@unpythonic.net>,
	Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org,
	kirill.shutemov@linux.intel.com, herbert@gondor.apana.org.au,
	Andi Kleen <ak@linux.intel.com>
References: <5603004A.20801@gmail.com>
 <20150923232841.GK1747@two.firstfloor.org>
 <5603E083.8020004@gmail.com>
 <20150924131235.GB6841@thunk.org>
 <56041E2C.2030602@gmail.com>
 <20150924165204.GA2835@unpythonic.net>
 <56044ADB.5050102@gmail.com>
 <20150924201413.GA3989@thunk.org>
 <560532FC.1070601@gmail.com>
 <56059B8A.2010402@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <56059B8A.2010402@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Sep 25, 2015 at 03:07:54PM -0400, Austin S Hemmelgarn wrote:
> 
> Interestingly, based on what dieharder is already saying about performance,
> /dev/urandom is slower than AES_OFB (at least, on this particular system,
> happy to provide hardware specs if someone wants).

Yeah, not surprised by that.  We're currently using a crypto hash
instead of AES, which means we're not doing any kind of hardware
acceleration.

Crazy applications that want to spend 100% of the CPU generating
random numbers instead of you know, doing _useful_ work
notwithstanding, /dev/urandom never had high performance as one of its
design goals.  The assumption was that if you needed that kind of
performance, you would use a user-space cryptographic random number
generator.


					- Ted