lkml.org 
[lkml]   [2015]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [patch 3/3] vmstat: Create our own workqueue
From
Date
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 +
> > WQ_MEM_RECLAIM.
>
> 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
http://lkml.kernel.org/r/201510251952.CEF04109.OSOtLFHFVFJMQO@I-love.SAKURA.ne.jp .
If your series is not for backporting, please choose one from
the candidates. Can you accept the original patch at
http://lkml.kernel.org/r/201510212126.JIF90648.HOOFJVFQLMStOF@I-love.SAKURA.ne.jp
which implements (1) from the candidates?


\
 
 \ /
  Last update: 2015-10-31 04:01    [W:0.114 / U:0.236 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site