From owner-freebsd-bugs Sat Nov 7 06:10:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05907 for freebsd-bugs-outgoing; Sat, 7 Nov 1998 06:10:02 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05856 for ; Sat, 7 Nov 1998 06:09:59 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id GAA04945; Sat, 7 Nov 1998 06:10:01 -0800 (PST) Date: Sat, 7 Nov 1998 06:10:01 -0800 (PST) Message-Id: <199811071410.GAA04945@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: HighWind Software Information Subject: Re: kern/8500: FreeBSD 3.0 thread scheduler is broken Reply-To: HighWind Software Information Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/8500; it has been noted by GNATS. From: HighWind Software Information To: peter@netplex.com.au Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/8500: FreeBSD 3.0 thread scheduler is broken Date: Sat, 7 Nov 1998 09:08:05 -0500 (EST) Okay.. I buy your explanation. FreeBSD's low level read()/write() are always blocking through the kernel when talking to UFS. That certainly will make it hard to do task switching. I think the right thing to do is to count that time and allow that time to effect when the thread switch happens. HOWEVER, I'm certainly willing to try aio_read/aio_write. WHERE IS THAT STUFF? I found "sys/aio.h", however, I can't find any library that has it. Nor can I find "aio_read" in any .c files in /usr/src. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message