On Wed 21-10-15 09:49:07, Christoph Lameter wrote: > On Wed, 21 Oct 2015, Michal Hocko wrote: > > > Because all the WQ workers are stuck somewhere, maybe in the memory > > allocation which cannot make any progress and the vmstat update work is > > queued behind them. > > > > At least this is my current understanding. > > Eww. Maybe need a queue that does not do such evil things as memory > allocation? I am not sure how to achieve that. Requiring non-sleeping worker would work out but do we have enough users to add such an API? I would rather see vmstat using dedicated kernel thread(s) for this this purpose. We have discussed that in the past but it hasn't led anywhere. Anyway the workaround for this issue seems to be pretty trivial and shouldn't affect users out of direct reclaim much so it sounds good enough to me. Longterm we should really get rid of scan_reclaimable from the direct reclaim altogether. -- Michal Hocko SUSE Labs -- 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>