From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753712AbbJULri (ORCPT ); Wed, 21 Oct 2015 07:47:38 -0400 Received: from one.firstfloor.org ([193.170.194.197]:49083 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752475AbbJULrh (ORCPT ); Wed, 21 Oct 2015 07:47:37 -0400 Date: Wed, 21 Oct 2015 13:47:35 +0200 From: Andi Kleen To: George Spelvin Cc: ahferroin7@gmail.com, andi@firstfloor.org, jepler@unpythonic.net, linux-kernel@vger.kernel.org, linux@rasmusvillemoes.dk, tytso@mit.edu Subject: Re: Updated scalable urandom patchkit Message-ID: <20151021114735.GL3533@two.firstfloor.org> References: <20151013211030.30325.qmail@ns.horizon.com> <20151021082743.7990.qmail@ns.horizon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151021082743.7990.qmail@ns.horizon.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 21, 2015 at 04:27:43AM -0400, George Spelvin wrote: > After having worked out the basics of a non-blocking /dev/urandom read, > (patches poated; I'm hoping someone will comment on them!), I need to > work out the crypto. Can we just use my multi pool patch for now? It works and is actually scalable and does not require any new "cryptographic research" or other risks. The main concern I heard was code size. I addressed this in the latest version by making the new code depend on CONFIG_NUMA, which is generally not set on small systems. -Andi