From owner-freebsd-current Thu Nov 12 11:36:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12269 for freebsd-current-outgoing; Thu, 12 Nov 1998 11:36:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12262 for ; Thu, 12 Nov 1998 11:36:14 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id OAA23382; Thu, 12 Nov 1998 14:35:23 -0500 (EST) Date: Thu, 12 Nov 1998 14:35:23 -0500 (EST) Message-Id: <199811121935.OAA23382@highwind.com> From: HighWind Software Information To: marcs@znep.com CC: current@FreeBSD.ORG In-reply-to: (message from Marc Slemko on Thu, 12 Nov 1998 11:06:47 -0800 (PST)) Subject: Re: aio_write() doesn't work! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It works, it is just the aio_offset is being ignored. Shouldn't be > too hard to fix. Well.. That is the whole reason we are going to use it. We need a way to do thread-safe offset read's and write's. FreeBSD 3.0 doesn't have pread()/pwrite() yet. And it seems that most I/O isn't counted toward a thread's time slice. Our hope is that by doing async I/O's we can get around that problem. Unfortunately, it appears that the system call doesn't work. Where does that code live? I guess I'll open a bug report. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message