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? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
