SoylentNews is people
SoylentNews
Submitted via IRC for Bytram
How did MS-DOS decide that two seconds was the amount of time to keep the floppy disk cache valid?
MS-DOS 2.0 contained a disk read cache, but not a disk write cache. Disk read caches are important because they avoid having to re-read data from the disk. And you can invalidate the read cache when the volume is unmounted.
But wait, you don't unmount floppy drives. You just take them out.
IBM PC floppy disk drives of this era did not have lockable doors. You could open the drive door and yank the floppy disk at any time. The specification had provisions for reporting whether the floppy drive door was open, but IBM didn't implement that part of the specification because it saved them a NAND gate. Hardware vendors will do anything to save a penny.
[...] Mark Zbikowski led the MS-DOS 2.0 project, and he sat down with a stopwatch while Aaron Reynolds and Chris Peters tried to swap floppy disks on an IBM PC as fast as they could.
They couldn't do it under two seconds.
So the MS-DOS cache validity was set to two seconds. If two disk accesses occurred within two seconds of each other, the second one would assume that the cached values were still good.
I don't know if the modern two-second cache flush policy is a direct descendant of this original office competition, but I like to think there's some connection.
(Score: 2) by DannyB on Thursday September 26 2019, @06:07PM (1 child)
That is a problem confined to the design of the filesystem and firmware on the stick. Something "under the hood" from the POV of the person using the stick.
Every performance optimization is a grate wait lifted from my shoulders.
(Score: 2) by dry on Friday September 27 2019, @03:55AM
Unluckily most sticks firmware is designed to use some form of FAT and doesn't even consider something as simple as aligning a file systems 4kb sectors with the sticks sectors.