Would it make a difference if I cited that My intent on upping the limits so high and pushing the dirty expiry so far into the future was to *avoid* triggering background writeback. In fact, dirty memory during one of these tests never actually rose a bunch. Are you guys suggesting that if dirty memory gets high enough the writeback turns into an OOM dodger that preempts foreground I/O? What I was hoping for is for dirty writeback itself to be throttled and stay out of the way of foreground I/O. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
