From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 1 16:04:19 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EFF516A46D for ; Tue, 1 Nov 2005 16:04:19 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BA2743D73 for ; Tue, 1 Nov 2005 16:04:09 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jA1G3v6N097867; Tue, 1 Nov 2005 09:03:57 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <436791ED.8010808@samsco.org> Date: Tue, 01 Nov 2005 09:03:57 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dinesh Nair 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> In-Reply-To: <43676121.4030801@alphaque.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org Subject: Re: locking in a device driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 16:04:19 -0000 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