Date: Tue, 23 Feb 1999 06:30:44 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: Doug Rabson <dfr@nlsystems.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Panic in FFS/4.0 as of yesterday Message-ID: <Pine.LNX.4.04.9902230630010.20535-100000@feral-gw> In-Reply-To: <Pine.BSF.4.05.9902230836480.60339-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 23 Feb 1999, Doug Rabson wrote: > On Mon, 22 Feb 1999, Matthew Jacob wrote: > > > > > > > > > Check the code paths and look for B_ASYNC getting unset. I believe this > > > > is the correct patch. > > > > > > As I said before, the reads and writes in question are not delayed writes. > > > The reason I have a problem is that the i/o queue in the driver has grown > > > to an obscene length, increasing latency to unreasonable levels. Changing > > > the order of processing delayed writes is irrelavent to this problem. > > > > This isn't a new problem. When I did driver level clustering at Sun back in > > 1990, I was regularly seeing queue lengths in excess of 1000 for a 16MB > > memory Sparc2. > > Thats a lot of memory to be using in a 16Mb box. Was the machine still > usable with this kind of i/o load? > Not really for interactive performance, no. But it did keep serving files. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.04.9902230630010.20535-100000>