Image Map Image Map
Results 1 to 4 of 4

Thread: Caching hard drive controller functions?

  1. #1

    Default Caching hard drive controller functions?

    I would like to better understand how hard drive controllers with dedicated cache utilized their resources. What was the most optimal caching strategy used by vendors (what to store, and when)?
    Similar for IDE vs. SCSI? Was the cache used for reading, writing, or both? If the cache was used as a write buffer then it seem data might not be written to the hard drive before the machine might appear safe to power off.

  2. #2
    Join Date
    May 2009
    Blog Entries


    Hard drive controllers with built in caches had secret sauce caching routines. Not publicly known and often optimized for specific tasks meaning relatively poor for others. It worked in a similar fashion to the normal OS level caches storing frequently accessed data and reading ahead somewhat and allowing writes to be ordered for maximum throughput. Probably less efficient than the OS cache since the OS cache knows how the allocation is stored and can therefore load up small sections of critical data in advance. Of course, the caching controller's memory wasn't being taken from the system memory pool so memory limited servers didn't wind up having to use virtual memory to retain a disk cache.

    Caching can be used on both reads and writes. Yes, there is a chance for data loss if someone races to turn the server off hence attaching to a UPS providing time to shut down in a clean fashion.

  3. #3


    Or battery-backed memory in some controllers, so they could prevent data loss by writing pending data after power was back.

  4. #4


    Thank you.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts