> + /* > + * If reclaim is encountering dirty pages, it may be because > + * dirty pages are reaching the end of the LRU even though the > + * dirty_ratio may be satisified. In this case, wake flusher > + * threads to pro-actively clean up to a maximum of > + * 4 * SWAP_CLUSTER_MAX amount of data (usually 1/2MB) unless > + * !may_writepage indicates that this is a direct reclaimer in > + * laptop mode avoiding disk spin-ups > + */ > + if (file && nr_dirty_seen && sc->may_writepage) > + wakeup_flusher_threads(nr_writeback_pages(nr_dirty)); wakeup_flusher_threads() works, but seems not the pertinent one. - locally, it needs some luck to clean the pages that direct reclaim is waiting on - globally, it cleans up some dirty pages, however some heavy dirtier may quickly create new ones.. So how about taking the approaches in these patches? - "[PATCH 4/4] vmscan: transfer async file writeback to the flusher" - "[PATCH 15/17] mm: lower soft dirty limits on memory pressure" In particular the first patch should work very nicely with memcg, as all pages of an inode typically belong to the same memcg. So doing write-around helps clean lots of dirty pages in the target LRU list in one shot. Thanks, Fengguang -- 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
