From owner-freebsd-hackers Wed Sep 8 20:11:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (Postfix) with SMTP id 97A10156C2 for ; Wed, 8 Sep 1999 20:11:28 -0700 (PDT) (envelope-from nordwick@scam.xcf.berkeley.edu) Received: (qmail 70302 invoked by uid 27268); 9 Sep 1999 03:10:45 -0000 Message-ID: <19990909031045.70301.qmail@scam.xcf.berkeley.edu> To: Jonathan Lemon Cc: freebsd-hackers@freebsd.org Subject: Re: message queues for I/O (usenix paper) In-Reply-To: Your message of "Wed, 08 Sep 1999 21:12:20 CDT." <19990908211220.51724@right.PCS> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <70299.936846644.1@scam.XCF.Berkeley.EDU> Date: Wed, 08 Sep 1999 20:10:45 -0700 From: "Jayson Nordwick" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thank for the pointers to the mailing list... very enlightening. I am going to try to write up an API for it this weekend with some cooperation with others. I will then give it a first pass around the freebsd-hackers and linux-kernl mailing lists. There are a few unanswered questions as to what an event it and how to handle them between threads and processes, but the general structure of an event queue seems to be wanted by almost everybody. I am not convinced by the usenix paper that this is the right way to do things, yet. state management is a bitch and taken too lightly most of the time. -jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message