On Fri, Oct 03, 2003 at 10:05:52AM -0500, James Bottomley wrote: > Well, the patch isn't quite correct because if it's not going to probe > the cache it should set up a write through cache (or disabled cache) as > the default.
Alan's original patch is included in my patch. > Patrick's patch > > http://marc.theaimsgroup.com/?l=linux-scsi&m=106366112221507 > > Does get this right. I am re-rolling the patch based on current 2.6, plus a couple comments Christoph had, I'll resend to you and linux-scsi. > But my principle objection, as I've stated before, is that it isn't true > that we don't need to manage the caches of hot pluggable devices, fibre > channel being the counter example. I agree - the type of transport does not indicate the capabilties of the device. If connectors were free and took no space (yeh never), we would have usb, firewire, spi, and fcp available on all disk drives. But for some reason with USB, we are more likely to have devices that cannot handle mode sense page 8 (cache). So shove some code into the usb-storage driver, and make it possible to set policy allowing us to disable page 8 for any device. Though I do not see the utility in syncing the cache, especially given the failure to figure out the caching method. High end storage won't care (probably battery backed ram, redundant storage, and separate out-of-band monitoring facilities). If the cache sync fails, the best we can do is notify the user, we can't reissue the write or even tell the user what block failed to make it to disk, the best we can do is say "your hosed". -- Patrick Mansfield ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
