Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!mcsun!hp4nl!botter!star.cs.vu.nl!ast
From: ast@cs.vu.nl (Andy Tanenbaum)
Newsgroups: comp.os.minix
Subject: Re: Disk performance under Minix
Message-ID: <3084@ast.cs.vu.nl>
Date: 28 Aug 89 20:54:52 GMT
References: <21978@louie.udel.EDU> <2141@ditsyda.oz> <3076@ast.cs.vu.nl> <1989Aug28.153612.8689@utzoo.uucp>
Reply-To: ast@cs.vu.nl (Andy Tanenbaum)
Organization: VU Informatica, Amsterdam
Lines: 18

In article <1989Aug28.153612.8689@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>You might want to look at the souped-up stdio stuff we ship with C News.
>It's the fastest implementation of fread, fwrite, fgets, and fputs we
>know of.  It is somewhat AT&T-Unix-stdio-specific in its details, but the
>methods should apply widely.
As you no doubt know, the MINIX stdio internal data structures are not the
same as AT&Ts (If they were, we'd have lawsuit problems).  This probably
means that if will be difficult to take over some of your stdio and leave
the rest the old way.  If anybody wants to volunteer for redoing stdio
using Henry's stuff, by all means do so.  I'll happily include it if it
it works, is robust, is clean code and is fast.

I don't have the time to look at it myself now.

Classes start next week and I have to finish off the third edition of the
architecture book.

Andy Tanenbaum (ast@cs.vu.nl)