![]() | |||||||||||
Messages in this thread |
On Wednesday August 16, dgc@sgi.com wrote: > > IMO, if you've got slow writeback, you should be reducing the amount > of dirty memory you allow in the machine so that you don't tie up > large amounts of memory that takes a long time to clean. Throttle earlier > and you avoid this problem entirely. I completely agree that 'throttle earlier' is important. I just not completely sure what should be throttled when. I think I could argue that pages in 'Writeback' are really still dirty. The difference is really just an implementation issue. So when the dirty_ratio is set to 40%, that should apply to all 'dirty' pages, which means both that flagged as 'Dirty' and those flagged as 'Writeback'. So I think you need to throttle when Dirty+Writeback hits dirty_ratio (which we don't quite get right at the moment). But the trick is to throttle gently and fairly, rather than having a hard wall so that any one who hits it just stops. Thanks, NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2006-08-17 06:11 [from the cache] ©2003-2008 | |||||||||||