Date: Tue, 31 Jan 2006 13:40:49 -0500 From: John Baldwin <jhb@freebsd.org> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/conf files options src/sys/kern kern_rwlock.c subr_lock.c src/sys/sys lock.h rwlock.h Message-ID: <200601311340.51250.jhb@freebsd.org> In-Reply-To: <20060128141445.GC2341@turion.vk2pj.dyndns.org> References: <200601272313.k0RNDQHI064747@repoman.freebsd.org> <20060128141445.GC2341@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 28 January 2006 09:14, Peter Jeremy wrote: > On Fri, 2006-Jan-27 23:13:26 +0000, John Baldwin wrote: > > Log: > > Add a basic reader/writer lock implementation to the kernel. > > Thank you. This looks interesting. > > > Tested on: i386 (4 cpu box with a kernel module that used 4 threads > > that randomly chose between read locks and write locks > > that ran w/o panicing for over a day solid. It usually > > panic'd within a few seconds when there were bugs during > > testing. :) The kernel module source is available on > > request.) > > Can I suggest that this module be committed into tools/regression or > similar so that it is generally available. I can I guess. I have 3 currently (crash, evtest, and crash2 (which is the latest one that uses multiple threads, crash just has a single thread)). -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601311340.51250.jhb>