Date: Tue, 12 Sep 2000 16:18:57 +0930 From: Greg Lehey <grog@lemis.com> To: Mark Murray <mark@grondar.za> Cc: Jason Evans <jasone@canonware.com>, John Baldwin <jhb@pike.osd.bsdi.com>, FreeBSD-arch@FreeBSD.org Subject: Re: cvs commit: src/sys/conf files src/sys/sys random.h src/sys/dev/randomdev hash.c hash.h harvest.c randomdev.c yarrow.c yarro Message-ID: <20000912161857.B23948@wantadilla.lemis.com> In-Reply-To: <200009120601.e8C611X75116@grimreaper.grondar.za>; from mark@grondar.za on Tue, Sep 12, 2000 at 08:01:00AM %2B0200 References: <20000911171819.A31089@blitz.canonware.com> <200009120601.e8C611X75116@grimreaper.grondar.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 12 September 2000 at 8:01:00 +0200, Mark Murray wrote: >> A general discussion of high level locking strategy is in order, but in my >> opinion, Mark's code is not an appropriate harbinger, since there's >> absolutely nothing wrong with the approach he took, regardless of the >> results of high level discussion. The issue we need to decide on is how to >> avoid bad interactions (read deadlock/livelock) between mutex hierarchies, >> but the randomdev mutex basically stands alone, so isn't subject to those >> discussions. > > I kinda winged it on this one, but I had the assistance of folk online. > It would be good to have some hardcore documentation. Indeed. I'm thinking of doing something, but don't mistake thinking for promising :-) Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000912161857.B23948>