From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 5 17:00:10 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7AB1516A401 for ; Thu, 5 Apr 2007 17:00:10 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 2FC1B13C44C for ; Thu, 5 Apr 2007 17:00:10 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 3490420F1; Thu, 5 Apr 2007 19:00:03 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id BAFA620B7; Thu, 5 Apr 2007 18:59:59 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id 8A606A10C0; Wed, 4 Apr 2007 09:49:04 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Kevin Sanders" References: <375baf50704031651p594e82e7y9f3d9c099f5d8268@mail.gmail.com> Date: Wed, 04 Apr 2007 09:49:03 +0200 In-Reply-To: <375baf50704031651p594e82e7y9f3d9c099f5d8268@mail.gmail.com> (Kevin Sanders's message of "Tue, 3 Apr 2007 16:51:09 -0700") Message-ID: <86k5wsinps.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: kqueue (9) 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: Thu, 05 Apr 2007 17:00:10 -0000 "Kevin Sanders" writes: > I'm trying to gain a better understanding of how kqueue's work from the > driver side. I've managed to glean enough information from the source of > other drivers, but I'm having a problem in my own kernel module when it is > unloaded. Specifically, when my module is unloaded and there are user > programs that have kqueue's with open descriptors from my driver in them,= I > don't know how to close things down from the driver side. Any advice or > links would be appreciated. Thanks in advance. This is usually handled by refusing to unload the module if it still as active consumers. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no