From owner-freebsd-arch Sat Jun 30 16:27:28 2001 Delivered-To: freebsd-arch@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C3E6737B406; Sat, 30 Jun 2001 16:27:24 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id BAA13888; Sun, 1 Jul 2001 01:27:20 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Jonathan Graehl" Cc: , Subject: Re: New kqueue filter References: <000301c101a3$62b04220$6dfeac40@straylight.com> From: Dag-Erling Smorgrav Date: 01 Jul 2001 01:27:19 +0200 In-Reply-To: <000301c101a3$62b04220$6dfeac40@straylight.com> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Jonathan Graehl" writes: > Jonathan Lemon can speak to this better than I, but I believe this is > because kevents are supposed to be level and not edge-sensitive (that > is, "there is data waiting", not "data became available"). The filter > would run the first time to place the event in the kqueue tentatively, > and then (some time later, when some other process could have removed > the event) when the user retrieves events with kevent, the filters run > again to verify that the condition still exists. No, the filter function isn't called at all until I actually type something on the tty, then it runs (and succeeds) twice in a row before the userland kqueue() call returns. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message