From owner-freebsd-threads@FreeBSD.ORG Mon Jul 14 10:55:00 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B965737B47B for ; Mon, 14 Jul 2003 10:54:59 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC2E243F75 for ; Mon, 14 Jul 2003 10:54:58 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38ldu3s.dialup.mindspring.com ([209.86.248.124] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19c7XH-000363-00; Mon, 14 Jul 2003 10:54:52 -0700 Message-ID: <3F12EE22.A145A9B5@mindspring.com> Date: Mon, 14 Jul 2003 10:53:38 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Petri Helenius References: <003501c348ad$a599fba0$812a40c1@PETEX31> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a46ba338030ad9f7623eba5dcc82691eaf3ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: freebsd-threads@freebsd.org cc: Julian Elischer cc: Andrew Gallatin Subject: Re: dumb KSE question X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 17:55:00 -0000 Petri Helenius wrote: > The cv I=B4m talking about would be signaled by a device driver which > shares some memory with the netgraph device node and the question > is about if in the ng_device like thing I can have the d_ioctl_t block > on the cv. People always want to do this sort of thing, but it's a really bogus thing to want to do. The problem with it is that you are crossing a protection domain, and, in doing that, all bets are off, in terms of allowable locking, etc.. The big issue you are going to hit is that you will deadlock. The proper thing to do is perform a blocking operation on the device itself, and unblock it when the condition is true in order to signal the user space process. -- Terry