Andrew Valencia <vandys@cisco.com> writes:
> It's up!
Great! Its nice to know that the driver is up and running on another
system and I haven't coded anything that's grossly dependent on
my particular hardware setup.
> It doesn't appear to be splitting I/O into 64K chunks; I'm getting
> I/O failures instead. I bet your FAT table isn't 126976 bytes, is it? :-)
> Well, my 260 meg DOS partition isn't named "FATBOY" for nothing!
The driver should be splitting I/O up into 4K chunks (cam_maxio). Is
there a 64K boundry problem on PC's that I'm not aware of?
> We need to fix that up eventually, but I'm going to change the DOS
> filesystem for now. All he does once he's running is sector I/O, so
> it seems silly to have him doing this one humongous I/O up front. Once
> he's running the only way he'll generate an I/O this big is if a whole
> bunch of your FAT was modified all at once. Not too likely.
Your right, but the driver should be able to handle large disk I/O
requests without a problem (tape I/O is another issue).
Mike Larson
Received on Thu Dec 23 18:54:40 1993
This archive was generated by hypermail 2.1.8 : Wed Sep 21 2005 - 21:01:53 PDT