Article View: comp.sys.mac
Article #41453Re: Mac II I/O rates vs. block size
From: Jonathan Pratt
Date: Wed, 26 Apr 1989 23:59
Date: Wed, 26 Apr 1989 23:59
17 lines
1272 bytes
1272 bytes
In article <39736@think.UUCP> ephraim@think.COM (Ephraim Vishniac) writes:
>
>Plainly, FSWrite has serious brain damage. Fortunately, substituting
>PBWrite is trivial and yields large improvements for larger block
>sizes.
>
This is a bit hard to swallow. In every development system I've looked
at FSWrite simply fills out a parameter block and calls the _Write trap.
Doesn't PBWrite simply call _Write with the ParmBlkPtr you've supplied?
Shouldn't be any difference. I would bet the problem is elsewhere.
Jonathan
/* Jonathan Pratt Internet: pratt@boulder.colorado.edu *
* Campus Box 525 uucp: ..!{ncar|nbires}!boulder!pratt *
* University of Colorado *
* Boulder, CO 80309 Phone: (303) 492-4293 */
Technical Details
Message-ID:
<8414@boulder.Colorado.EDU>Path:
arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!boulder!prattReferences:
<39736@think.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!boulder!pratt From: pratt@boulder.Colorado.EDU (Jonathan Pratt) Newsgroups: comp.sys.mac Subject: Re: Mac II I/O rates vs. block size Message-ID: <8414@boulder.Colorado.EDU> Date: 26 Apr 89 23:59:40 GMT References: <39736@think.UUCP> Sender: news@boulder.Colorado.EDU Reply-To: pratt@boulder.Colorado.EDU (Jonathan Pratt) Organization: University of Colorado, Boulder Lines: 17