Date: Tue, 12 Sep 2000 08:01:00 +0200 From: Mark Murray <mark@grondar.za> To: Jason Evans <jasone@canonware.com> Cc: Greg Lehey <grog@lemis.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: <200009120601.e8C611X75116@grimreaper.grondar.za> In-Reply-To: <20000911171819.A31089@blitz.canonware.com> ; from Jason Evans <jasone@canonware.com> "Mon, 11 Sep 2000 17:18:19 MST." References: <20000911171819.A31089@blitz.canonware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Mark's changes to randomdev are very straight-forward, and they use a mutex > exactly as a mutex should be used (though a condition variable will help > make things even cleaner, once they're available). This is good to know; thanks! :-) > 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. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org 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?200009120601.e8C611X75116>