🚀 go-pugleaf

Date Entered: 01-23-93 18:08
C(> 
C(> >Didn't he say it was a VL card?  That means that the CPU can't do
C(> >anything anyway, since when the disk controller has the local bus the
C(> >CPU can't talk to memory or anything anyway.  This is why I don't see
C(> >VL as a real win for anything except perhaps video; it will give you
C(> >great burst mode numbers, but it impacts overall system performance to
C(> >do that.  
C(> 
C(> Hmmm, it still has the internal I/D cache to run out of.

    Could you explain this to me a little slower please?  I am about 
to plunk down big bucks on a new system.  This particular vendor 
offers local bus hard disk controller.  He says the bus is 100% VESA 
compatible.  
    It seems to me that local bus disk access will be a speed booster 
for the reason of faster data communicatio with the CPU / memory.  It 
is four times faster to get data off the disk at 33 MHz off the local 
bus connection to the CPU and memory than at 8 MHz via the ISA bus. 
As simple as that... no?   Why would this impact system performance 
any more than getting data off the ISA bus.
    The only way I see the latter happening is if normally (i.e. using
 a ISA bus) data can go from disk controller to memory directly (DMA) 
while the CPU is doing something else, while with a local bus, Data 
transfer from hard disk controller to memory has to go via the CPU 
(i.e. no DMA) and then to memory.   Is this what happens?
    Please help me out with this before I toss big bucks down the 
toilet.
                       Thanks,
                        Gyl
---
   RR 1.60 R001881
   RoseMail 2.00 : RoseNet<=>Usenet Gateway : Rose Media 416-733-2285