MMC quirks relating to performance/lifetime.
From: Andrei Warkentin <hidden>
Date: 2011-02-14 19:29:59
Also in:
linux-mmc
On Sun, Feb 13, 2011 at 11:39 AM, Arnd Bergmann [off-list ref] wrote:
I don't think it needs to be boot-time, it can easily be run-time tuneable using sysfs, where you can configure it using an init script or some other logic from user space.
True, definitely expose the controls through sysfs.
Yes. What is "PE" here?
Ah sorry, I had to look that one up myself, I thought it was the local jargon associated with the problem space :-). Program/Erase cycle.
quoted
So T suggested for random data to better go into buffer A. How? Two suggestions. 1) Split smaller accesses into 8KB and write with reliable write. 2) Split smaller accesses into 8KB and write in reverse. The patch does both and I am verifying if that is really necessary. I need to go see the mmc spec and what it says about reliable write.I should add this to my test tool once I can reproduce it. If it turns out that other media do the same, we can also trigger the same behavior for those.
As I mentioned, I am checking with T right now on whether we can use suggestion (1) or suggestion (2) or if they need to be combined. The documentation we got was open to interpretation and the patch created from that did both. You mentioned that writing in reverse is not a good idea. Could you elaborate why? I would guess because you're always causing a write into a different AU (on these Toshiba cards), causing extra GC on every write?
quoted
Basically, whatever behavior you choose is going to be wrong some set of cards. Which is why tuning it probably only makes sense for eMMC parts, and should be a set of runtime/compile-time quirks. What do you think?Your explanation makes sense, but I'd definitely favor a run-time solution over compile-time or boot-time, because it would be much more flexible. We should also be able to find some optimizations that are universally good so we can always use them.
Then that's the angle I will pursue. It is the most flexible and then you don't have to pollute the block driver with little workarounds for soon-to-be-obsolete hardware. Hopefully I'll have something for re-review soon. Thanks Again!