On Thu, Oct 22, 2015 at 05:06:23PM +0200, Michal Hocko wrote: > Do I get it right that if vmstat_update has its own workqueue with > WQ_MEM_RECLAIM then there is a _guarantee_ that the rescuer will always > be able to process vmstat_update work from the requested CPU? Yeah. > That should be sufficient because vmstat_update doesn't sleep on > allocation. I agree that this would be a more appropriate fix. The problem seems to be reclaim path busy looping waiting for vmstat_update and workqueue thinking that the work item must be making forward-progress and thus not starting the next work item. Thanks. -- tejun -- 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>