Date: Thu, 03 Nov 2005 04:52:41 +0800 From: Dinesh Nair <dinesh@alphaque.com> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-hackers@freebsd.org Subject: Re: locking in a device driver Message-ID: <43692719.90805@alphaque.com> In-Reply-To: <20051102.121248.74711520.imp@bsdimp.com> References: <4361044B.50807@alphaque.com> <20051027.205250.55834228.imp@bsdimp.com> <43690424.1040904@alphaque.com> <20051102.121248.74711520.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/03/05 03:12 Warner Losh said the following: > Yes. if you tsleep with signals enabled, the periodic timer will go > off, and you'll return early. This typically isn't what you want > either. looks like i've got a lot of work to do, poring thru all the ioctls for the device and trying to use another method to wait instead of tsleep(). > works. If you use libc_r on 5, you'll see exactly this behavior. If > you use libpthread or libthr, you won't. i use gcc -pthread, so it's libc_r on 4.x. what does 'gcc -pthread' link to on 5.x ? -- 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?43692719.90805>