Date: Wed, 04 Apr 2007 09:49:03 +0200 From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Kevin Sanders" <newroswell@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: kqueue (9) Message-ID: <86k5wsinps.fsf@dwp.des.no> In-Reply-To: <375baf50704031651p594e82e7y9f3d9c099f5d8268@mail.gmail.com> (Kevin Sanders's message of "Tue, 3 Apr 2007 16:51:09 -0700") References: <375baf50704031651p594e82e7y9f3d9c099f5d8268@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Kevin Sanders" <newroswell@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86k5wsinps.fsf>