Date: Fri, 28 Oct 2005 00:46:03 +0800 From: Dinesh Nair <dinesh@alphaque.com> To: Scott Long <scottl@samsco.org> Cc: freebsd-hackers@freebsd.org Subject: Re: locking in a device driver Message-ID: <4361044B.50807@alphaque.com> In-Reply-To: <4360DD7B.20900@samsco.org> References: <435EEC56.9080708@samsco.org> <200510261130.45506.jhb@freebsd.org> <435FA6A9.4000600@samsco.org> <200510261324.03790.jhb@freebsd.org> <4360B8EE.4070605@alphaque.com> <4360DD7B.20900@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/27/05 22:00 Scott Long said the following: > are doing. Other than that, there likely isn't anything that you need > to do for 'locking' in 4.x. The kernel is non-reentrant there, so you > don't need to worry about synchronizing multiple threads. thanx a bunch, scott. it's been a nightmare trying to debug the driver and to try to find out why the driver compiled from the same source tree works on freebsd 5.x and doesnt work at all on freebsd 4.x . so far, i've been gloriously unsuccesful at this, and am getting at my wits end on what to go look at. the userland application uses pthreads, and works like a charm both on 4.x and 5.x without using the device. however, when the device is used, it somehow has synchronization errors on 4.x, leading to timers (created in the userland app) timing out and the like. -- Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4361044B.50807>