This message is from the T13 list server.
Only the FUA command's data would be affected. Since a FLUSH command already affects all commands in the write cache and FLUSH adversely affects performance, the FUA command gives us the ability to target specific requests as non-cacheable so we can "atomically" put critical information on the disk. Regards, MKE. -----Original Message----- From: Hale Landis [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 7:47 AM To: T13 List Server Subject: Re: [t13] ATA-7 Write DMA Queued FUA EXT problem This message is from the T13 list server. Does FUA mean access the media ONLY for the single command that requests FUA or for all data currently in the "write cache" (basically combining the effect of some writes followed by a FLUSH CACHE) or is it something far more complex (and therefore more subject to failure?). Did the requester of this "feature" ever provide more info or a better description of what it was they really wanted? Hale *** Hale Landis *** www.ata-atapi.com ***
