Re: [patch 3/3] vmstat: Create our own workqueue

From: Tetsuo Handa
Date: Fri Oct 30 2015 - 22:43:11 EST

Christoph Lameter wrote:
> On Thu, 29 Oct 2015, Tejun Heo wrote:
> > Wait, this series doesn't include Tetsuo's change. Of course it won't
> > fix the deadlock problem. What's necessary is Tetsuo's patch +
> This series is only dealing with vmstat changes. Do I get an ack here?

Then, you need to update below description (or drop it) because
patch 3/3 alone will not guarantee that the counters are up to date.

Christoph Lameter wrote:
> Seems that vmstat needs its own workqueue now since the general
> workqueue mechanism has been *enhanced* which means that the
> vmstat_updates cannot run reliably but are being blocked by
> work requests doing memory allocation. Which causes vmstat
> to be unable to keep the counters up to date.

I am waiting for decision from candidates listed at .
If your series is not for backporting, please choose one from
the candidates. Can you accept the original patch at
which implements (1) from the candidates?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at