From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161775AbcE3Rx1 (ORCPT ); Mon, 30 May 2016 13:53:27 -0400 Received: from one.firstfloor.org ([193.170.194.197]:52786 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161249AbcE3Rx0 (ORCPT ); Mon, 30 May 2016 13:53:26 -0400 Date: Mon, 30 May 2016 10:53:22 -0700 From: Andi Kleen To: "Theodore Ts'o" Cc: Linux Kernel Developers List , smueller@chronox.de, herbert@gondor.apana.org.au, andi@firstfloor.org, sandyinchina@gmail.com, cryptography@lakedaemon.net, jsd@av8n.com, hpa@zytor.com, linux-crypto@vger.kernel.org Subject: Re: [PATCH-v3 0/5] random: replace urandom pool with a CRNG Message-ID: <20160530175322.GB13997@two.firstfloor.org> References: <1464586765-14436-1-git-send-email-tytso@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1464586765-14436-1-git-send-email-tytso@mit.edu> 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 > In addition, on NUMA systems we make the CRNG state per-NUMA socket, to > address the NUMA locking contention problem which Andi Kleen has been > complaining about. I'm not entirely sure this will work well on the > crazy big SGI systems, but they are rare. Whether they are rarer than It should work the same on larger systems, the solution scales naturally to lots of sockets. It's not clear it'll help enough on systems with a lot more cores per socket, like a Xeon Phi. But for now it should be good enough. -Andi