From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753656AbaHEOvu (ORCPT ); Tue, 5 Aug 2014 10:51:50 -0400 Received: from qmta05.emeryville.ca.mail.comcast.net ([76.96.30.48]:38799 "EHLO qmta05.emeryville.ca.mail.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751173AbaHEOvt (ORCPT ); Tue, 5 Aug 2014 10:51:49 -0400 Date: Tue, 5 Aug 2014 09:51:44 -0500 (CDT) From: Christoph Lameter To: Sasha Levin cc: akpm@linux-foundation.org, Gilad Ben-Yossef , Thomas Gleixner , Tejun Heo , John Stultz , Mike Frysinger , Minchan Kim , Hakan Akkan , Max Krasnyansky , Frederic Weisbecker , "Paul E. McKenney" , linux-kernel@vger.kernel.org, linux-mm@kvack.org, hughd@google.com, viresh.kumar@linaro.org, hpa@zytor.com, mingo@kernel.org, peterz@infradead.org Subject: Re: vmstat: On demand vmstat workers V8 In-Reply-To: <53DFFD28.2030502@oracle.com> Message-ID: References: <53D31101.8000107@oracle.com> <53DFFD28.2030502@oracle.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 4 Aug 2014, Sasha Levin wrote: > On 07/25/2014 10:22 PM, Sasha Levin wrote: > > On 07/10/2014 10:04 AM, Christoph Lameter wrote: > >> > This patch creates a vmstat shepherd worker that monitors the > >> > per cpu differentials on all processors. If there are differentials > >> > on a processor then a vmstat worker local to the processors > >> > with the differentials is created. That worker will then start > >> > folding the diffs in regular intervals. Should the worker > >> > find that there is no work to be done then it will make the shepherd > >> > worker monitor the differentials again. > > Hi Christoph, all, > > > > This patch doesn't interact well with my fuzzing setup. I'm seeing > > the following: > > I think we got sidetracked here a bit, I've noticed that this issue > is still happening in -next and discussions here died out. Ok I saw in another thread that this issue has gone away. Is there an easy way to reproduce this on my system?