Date: Thu, 03 Nov 2005 04:55:10 +0800 From: Dinesh Nair <dinesh@alphaque.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-hackers@freebsd.org, julian@elischer.org Subject: Re: locking in a device driver Message-ID: <436927AE.4030809@alphaque.com> In-Reply-To: <20051102.132709.101593999.imp@bsdimp.com> References: <20051027.205250.55834228.imp@bsdimp.com> <43690424.1040904@alphaque.com> <43690EED.10703@elischer.org> <20051102.132709.101593999.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/03/05 04:27 M. Warner Losh said the following: > that this is the case: sleep in an ioctl, and the entire process hangs > until the ioctl returns. which is probably what's happening in my case. i've got 4 threads spun off, and one thread reads what the other writes and vice versa. after writing, a thread goes off into an ioctl or a read where a tsleep() is executed. this would block the reader thread as well if libc_r were to be used, as is what i am using. -- 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?436927AE.4030809>