From owner-freebsd-questions Thu Feb 16 20:49:58 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA14428 for questions-outgoing; Thu, 16 Feb 1995 20:49:58 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id UAA14422 for ; Thu, 16 Feb 1995 20:49:55 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA16408; Thu, 16 Feb 95 21:43:51 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9502170443.AA16408@cs.weber.edu> Subject: Re: Async I/O for FreeBSD 2.0 To: mhg@sampson.ccsf.caltech.edu (Marc Goroff) Date: Thu, 16 Feb 95 21:43:50 MST Cc: questions@FreeBSD.org In-Reply-To: <199502162335.PAA02959@sampson.ccsf.caltech.edu> from "Marc Goroff" at Feb 16, 95 03:35:47 pm X-Mailer: ELM [version 2.4dev PL52] Sender: questions-owner@FreeBSD.org Precedence: bulk > I have just installed FreeBSD 2.0 and it is performing very well, but I > have an application that requires async I/O. Has anyone implemented > aioread or aiowrite for FreeBSD 2.0???? I did once back when LWP was really the way you did threads. I did an LWP, too, writing it first for Sun using Sun's aioread/write/wait/cancel. It's relatively trivial (lot of grunt work), but my code is not at all applicable to the 2.0 source base. You will to add aiowait and aiocancel as well. A useful document is available from the CS department of Washington State (wuarchive), called "User space Threads and Register Windowing on SPARC" or something like that. You will need to add a context block to the current proc for each outstanding I/O if you expect to use SIGIO; if you always use aiowait, then it's even easier. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.