> I'm pretty certain that most DOS installations use a minimal setting for > the BUFFERS= directive in config.sys. I've never seen anything over 30.
As a little known fact: for FreeDOS, "BUFFERS=10" is implemented as "at least 10, or whatever fits into HIGH memory" "BUFFERS=-10" means "exactly 10 sectors" > Cache pollution is not an issue when your cache is already tiny - it's > always being flooded. The BUFFERS cache primary exists to pick up the easy > case of sectors being read or modified close in time, like during a FAT > update before extending a file or reading the next cluster number from the > FAT when doing a sequential read. And they have their biggest impact on > floppy accesses, which are horrible. > Look at it like this .. loading almost any program is going to wipe out > the buffers cache. nope. reading multiple sectors for file data (and that's the only case where multiple sectors are read) doesn't go through the cache at all. At least that was the case in ~2003. So the BUFFERS cache is mostly for caching FAT, directory structure, and reading files in small chunks. > We're not protecting anything by keeping INT 25/26 > traffic out of it. +1 INT 25/26 traffic should behave as other kernel traffic, with (for certainty) have a "flush dirty sectors" after each INT 26 WRITE request (just in case it might be buffered). Tom _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
