From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 14 10:46:24 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF3A616A407 for ; Sat, 14 Oct 2006 10:46:24 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd3mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F4EF43D49 for ; Sat, 14 Oct 2006 10:46:24 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd2mr3so.prod.shaw.ca (pd2mr3so-qfe3.prod.shaw.ca [10.0.141.108]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J74003FWGLCQ680@l-daemon> for freebsd-hardware@freebsd.org; Sat, 14 Oct 2006 04:46:25 -0600 (MDT) Received: from pn2ml10so.prod.shaw.ca ([10.0.121.80]) by pd2mr3so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7400J2SGLCDPU0@pd2mr3so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Sat, 14 Oct 2006 04:46:24 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7400IUCGLCYVD0@l-daemon> for freebsd-hardware@freebsd.org; Sat, 14 Oct 2006 04:46:24 -0600 (MDT) Date: Sat, 14 Oct 2006 03:46:22 -0700 From: soralx@cydem.org In-reply-to: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> To: freebsd-hardware@freebsd.org Message-id: <200610140346.22554.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> User-Agent: KMail/1.9.1 Subject: Re: Quiet computer X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2006 10:46:24 -0000 > single core. Yes, I realize that the woodcrest is faster than above > mentioned cpu, but a 100x speed difference? That doesn't seem realistic > to me (although if those are valid results, I'd be pretty happy with > that)... Even if VIA's true RNG is actually being used, then I see how this could be realistic. The pseudo-RNG in you machine constitutes a mathematical algorithm with an initial random seed (yarrow, if I'm not mistaken). You have a fast CPU, and it crunches numbers rapidly; thus, you get that impressive speed. For a true RNG, every bit provided is original, random (not a result of some transformation). So, if the hardware portion has limited bandwith (randomness 'regenerates' slowly -- bits don't change fast enough), or there's delay along the path, then RNG device speed will be limited -- and therefore encryption speed as well (if I'm not mistaken). But if the randomness source is slow, it's not a big problem. For example, a chip can be used that's meant to transform, or 'dilute', the truly random stream somewhat to increase speed. Hmm... OTOH, noone yet complained about quantum processes being too slow, so I suppose /dev/urandom is not what we want to test. When we see some performance data for the VIA CPU, then we'll determine whether it's TRNG spitting out the random bits or is it the yarrow that's increasing entropy :) BTW, David, test (if you have enough time for curiosity) /dev/urandom (or wherever the generator is) with different values of 'bs', from very small to large (1 byte, 512, 4k, 16k, 64k) to see how much it depends on block size. > bash-2.05b$ time dd if=/dev/urandom bs=1024 count=10240 of=/dev/null > 10240+0 records in > 10240+0 records out > 10485760 bytes transferred in 0.154649 secs (67803598 bytes/sec) >Bucky [SorAlx] ridin' VN1500-B2