Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!bu.edu!transfer!lectroid!jjmhome!crackers!cpoint!frog!rmkhome!rmk
From: rmk@rmkhome.UUCP (Rick Kelly)
Newsgroups: comp.unix.sysv386
Subject: Re: Performance in 486 EISA machines:  ISC vs. SCO
Message-ID: <9105242244.15@rmkhome.UUCP>
Date: 25 May 91 07:43:00 GMT
References: <49397@ut-emx.uucp>
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats
Lines: 26

In article <49397@ut-emx.uucp> solomon@chaos.utexas.edu (Thomas Solomon) writes:
[ ISC and SCO stuff deleted ]
>A few other questions:  do either (or both) of these unices support
>486-specific commands (presumably increasing efficiency)?  How about
>features specific to the EISA bus, such as bus mastering (very important
>for high throughput in disk access) and DMA, and 33 MHz burst mode?  Also,
>can either (or both) handle _synchronous_ SCSI transfers to disk?

Bus mastering is not EISA specific.  Micronics, Intel, and Mylex all build
386 33 mhz ISA motherboards that support bus masters, and will do
synchronous transfer with Adaptec AHA-154xx SCSI controllers.

If SCO and ISC don't have support in their drivers, they are just plain lazy.

>For the record, we are planning on purchasing an Austin Computer Systems
>486/33 MHz EISA machine with an EISA, SCSI, non-caching disk controller
>(probably the UltraStor 24F), and a Seagate Elite (ST41600N) SCSI disk
>(rated for 3Mbytes/sec internal transfer rate).  We want to get an 
>operating system that will take advantage of all the performance of
>this machine.  By the way, we are considering putting a DOS partition
>on the disk, and using DOS for real-time data-taking, then switch to
>unix for the analysis.

Or you could experiment with VPIX.

Rick Kelly	rmk@rmkhome.UUCP	frog!rmkhome!rmk	rmk@frog.UUCP