On Mon, 19 Apr 2010 11:08:05 +1000 Dave Chinner <david@xxxxxxxxxxxxx> wrote: > > Maybe we need to do the background dirty writes a bit more > > aggressive... or play with heuristics where we get an adaptive > > timeout (say, if the file got closed by the last opener, then do a > > shorter timeout) > > Realistically, I'm concerned about preventing the worst case > behaviour from occurring - making the background writes more > agressive without preventing writeback in LRU order simply means it > will be harder to test the VM corner case that triggers these > writeout patterns... while I appreciate that the worst case should not be uber horrific... I care a LOT about getting the normal case right... and am willing to sacrifice the worst case for that.. (obviously not to infinity, it needs to be bounded) -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
