You missed one: ordering shelves in hot zones so less used shelves are farther away.
Safaribooks already does that, and cheaper too. You even get tokens for watermarked drm-free offline versions.
While I don't doubt your facts, they never get mentioned as a reason and they don't get acted upon either:
- People reading heavy books aren't told to stow them
- People sleeping aren't awoken so they pay attention
- People with glasses aren't told to hang on to them
Furthermore, I would think that people will notice when they're about to crash and assume suitable positions, including quickly hanging on to loose items.
The electronic interference story is no good and everybody knows it. Heck, I don't turn off my laptop/phone - I switch it to sleep mode. It's still active...
The deadly projectile story is a lot better but presumably a lightweight phone or ebook reader won't be all that deadly, and whether it's on or off won't make a difference.
Wait, what? Oh I see - are you proposing to add a fully associative cache in front of the 4GB Flash memory to speed up cache lookups and thus lazily storing writes as well?
I thought you were caching the stored data in a cache. I must admit I kinda glossed over the "fully associative with write-back" bit
I suppose that can work - SLC is great for caching writes on. However, it's a lot more work than simply copying hot reads onto the Flash and caching them there. What you're proposing means a lot of new work on the disk controller, whereas now they simply slapped a caching thing on top of what they had.
However, at http://www.cs.umd.edu/class/sum2003/cmsc311/Notes/Memory/fully.html they explain fully associative caches nicely and add that "The hardware for finding the right slot, then picking the slot if more than one choice is available is rather large, so fully associative caches are not used in practice".
I don't think it really matters how Seagate exactly decides to cache stuff - right now they do read-cache only and it would be nice if they did a write-cache as well. You can do that just fine without using fully associative caches for the addressing.
Doing caching right is just not a trivial thing, especially if you have to do it on a tiny embedded platform.
- RAM is expensive
- The OS can do it better than the disk (except at boot time)
- Doing it right is not trivial (complicated firmware is a bad thing)
If you want a disk cache with write-back, buy more memory for your system, that's what the OS does with it.
Argh, I replied to this post but the useless iPhone interface made me actually reply to the topic. Can you please explain what is broken about loopback nfs? I can't find a recent reference anywhere...
Can you elaborate on that broken loopback NFS in Linux? I couldn't find anything about that, last mention of it being broken was in 2002.
You know, a lot of people use loopback nfs for crypto homedirs and I think fuse. I'd like to think that it isn't broken...
and then come back to educate other
Please don't confuse American prices with European prices. €359 is very reasonable over here - you won't find a laptop for that price over here either. The laptop you describe would be €600 if you're willing to stand in line at 8AM.
Remember, we pay around 20% in sales tax.
In another development Intel has updated its Itanium roadmap to include a new chip dubbed "Kittson" which will follow the release of Poulson- which will be based on a new microarchitecture that provides higher levels of parallelism. "There will be four or more cores, multithreading enhancements, and we'll also introduce more instructions to take advantage of parallelism, especially in virtualization." said William Wu, regional marketing manager for server platforms at Intel Asia-Pacific."