From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935945AbdEVVOV (ORCPT ); Mon, 22 May 2017 17:14:21 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37764 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933882AbdEVVOR (ORCPT ); Mon, 22 May 2017 17:14:17 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 2B93F61B8F Authentication-Results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=mtosatti@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 2B93F61B8F Date: Mon, 22 May 2017 18:13:41 -0300 From: Marcelo Tosatti To: Christoph Lameter Cc: Luiz Capitulino , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Rik van Riel , Linux RT Users , cmetcalf@mellanox.com Subject: Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration Message-ID: <20170522211337.GA4718@amt.cnet> References: <20170512154026.GA3556@amt.cnet> <20170512161915.GA4185@amt.cnet> <20170515191531.GA31483@amt.cnet> <20170519143407.GA19282@amt.cnet> <20170520082646.GA16139@amt.cnet> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Mon, 22 May 2017 21:14:16 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 22, 2017 at 11:38:02AM -0500, Christoph Lameter wrote: > On Sat, 20 May 2017, Marcelo Tosatti wrote: > > > > And you can configure the interval of vmstat updates freely.... Set > > > the vmstat_interval to 60 seconds instead of 2 for a try? Is that rare > > > enough? > > > > Not rare enough. Never is rare enough. > > Ok what about the other stuff that must be going on if you allow OS > activity like f.e. the tick, scheduler etc etc. Yes these are also problems... but we're either getting rid of them or reducing their impact as much as possible. vmstat_update is one member of the problematic set. I'll get you the detailed IPI measures, hold on...