Date: Tue, 01 Nov 2005 09:03:57 -0700 From: Scott Long <scottl@samsco.org> To: Dinesh Nair <dinesh@alphaque.com> Cc: freebsd-hackers@freebsd.org Subject: Re: locking in a device driver Message-ID: <436791ED.8010808@samsco.org> In-Reply-To: <43676121.4030801@alphaque.com> References: <4360B8EE.4070605@alphaque.com> <4360DD7B.20900@samsco.org> <4361044B.50807@alphaque.com> <20051027.205250.55834228.imp@bsdimp.com> <4361E3E0.4090409@alphaque.com> <43676121.4030801@alphaque.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dinesh Nair wrote: > > > On 10/28/05 16:40 Dinesh Nair said the following: > >> >> >> On 10/28/05 10:52 M. Warner Losh said the following: >> >>> libc_r will block all other threads in the application while an ioctl >>> executes. libpthread and libthr won't. I've had several bugs at work >> >> >> >> which is a Good Thing(tm) indeed for me on 4.x. > > > which may not be a Good Thing(tm) after all. this could be causing the > problem i'm seeing with the driver on 4.x. any methods to get around > this, short of not using threads ? > I think this thread has gone too far into hyperbole and conjecture. What is your code trying to do, and what problems are you seeing? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?436791ED.8010808>