From owner-freebsd-arch@FreeBSD.ORG  Tue Feb 24 17:40:57 2015
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 60ADE1B2
 for <freebsd-arch@freebsd.org>; Tue, 24 Feb 2015 17:40:57 +0000 (UTC)
Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 3529FBFA
 for <freebsd-arch@freebsd.org>; Tue, 24 Feb 2015 17:40:57 +0000 (UTC)
Received: from gold.funkthat.com (localhost [127.0.0.1])
 by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id t1OHer9W004332
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Tue, 24 Feb 2015 09:40:53 -0800 (PST)
 (envelope-from jmg@gold.funkthat.com)
Received: (from jmg@localhost)
 by gold.funkthat.com (8.14.5/8.14.5/Submit) id t1OHerSJ004331;
 Tue, 24 Feb 2015 09:40:53 -0800 (PST) (envelope-from jmg)
Date: Tue, 24 Feb 2015 09:40:53 -0800
From: John-Mark Gurney <jmg@funkthat.com>
To: Warner Losh <imp@bsdimp.com>
Subject: Re: locks and kernel randomness...
Message-ID: <20150224174053.GG46794@funkthat.com>
References: <20150224012026.GY46794@funkthat.com>
 <20150224015721.GT74514@kib.kiev.ua>
 <54EBDC1C.3060007@astrodoggroup.com>
 <20150224024250.GV74514@kib.kiev.ua>
 <DD06E2EA-68D6-43D7-AA17-FB230750E55A@bsdimp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DD06E2EA-68D6-43D7-AA17-FB230750E55A@bsdimp.com>
X-Operating-System: FreeBSD 9.1-PRERELEASE amd64
X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88  9322 9CB1 8F74 6D3F A396
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html
X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger?
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7
 (gold.funkthat.com [127.0.0.1]); Tue, 24 Feb 2015 09:40:53 -0800 (PST)
Cc: Konstantin Belousov <kostikbel@gmail.com>,
 Harrison Grundy <harrison.grundy@astrodoggroup.com>, freebsd-arch@freebsd.org
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2015 17:40:57 -0000

Warner Losh wrote this message on Tue, Feb 24, 2015 at 07:56 -0700:
> Then again, if you want to change random(), provide a weak_random() that???s
> the traditional non-crypto thing that???s fast and lockless. That would make it easy
> to audit in our tree. The scheduler doesn???t need cryptographic randomness, it
> just needs to make different choices sometimes to ensure its notion of fairness.

I do not support having a weak_random...  If the consumer is sure
enough that you don't need a secure random, then they can pick an LCG
and implement it themselves and deal (or not) w/ the locking issues...

It appears that the scheduler had an LCG but for some reason the authors
didn't feel like using it here..

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."