Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753480AbdDCOky (ORCPT ); Mon, 3 Apr 2017 10:40:54 -0400 Received: from mail-wr0-f196.google.com ([209.85.128.196]:35180 "EHLO mail-wr0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751633AbdDCOkw (ORCPT ); Mon, 3 Apr 2017 10:40:52 -0400 Date: Mon, 3 Apr 2017 16:40:49 +0200 From: Frederic Weisbecker To: Mike Galbraith Cc: Rik van Riel , Luiz Capitulino , Wanpeng Li , linux-kernel@vger.kernel.org Subject: Re: [BUG nohz]: wrong user and system time accounting Message-ID: <20170403144047.GA3820@lerouge> References: <20170323165512.60945ac6@redhat.com> <1490636129.8850.76.camel@redhat.com> <20170328132406.7d23579c@redhat.com> <20170329131656.1d6cb743@redhat.com> <1490818125.28917.11.camel@redhat.com> <1490848051.4167.57.camel@gmx.de> <20170330125157.GB3626@lerouge> <1490878951.28917.16.camel@redhat.com> <1490880922.4702.66.camel@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1490880922.4702.66.camel@gmx.de> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 927 Lines: 21 On Thu, Mar 30, 2017 at 03:35:22PM +0200, Mike Galbraith wrote: > On Thu, 2017-03-30 at 09:02 -0400, Rik van Riel wrote: > > On Thu, 2017-03-30 at 14:51 +0200, Frederic Weisbecker wrote: > > > > Also, why does it raise power consumption issues? > > > > On a system without either nohz_full or nohz idle > > mode, skewed ticks result in CPU cores waking up > > at different times, and keeping an idle system > > consuming power for more time than it would if all > > the ticks happened simultaneously. > > And if your server farm is mostly idle, that power savings may delay > your bankruptcy proceedings by a whole microsecond ;-) > > Or more seriously, what skew does do on boxen of size X today is > something for perf to say. At the time, removal was very bad for my 8 > socket box, and allegedly caused huge SGI beasts in horrific pain. I see. Nohz_full is already bad for powersavings anyway. CPU 0 always ticks :-)