Re: clocksource_watchdog causing scheduling of timers every second (was [v13] support "task_isolation" mode)

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Newsgroups	linux.kernel
Subject	Re: clocksource_watchdog causing scheduling of timers every second (was [v13] support "task_isolation" mode)
Date	Fri, 12 Aug 2016 18:20:01 +0200
Message-ID	<s5nlD-3VR-9@gated-at.bofh.it> (permalink)
References	<rYR58-6Qr-21@gated-at.bofh.it> <rYR58-6Qr-19@gated-at.bofh.it> <rZxxo-6F-9@gated-at.bofh.it> <s4K0W-2GI-29@gated-at.bofh.it> <s4TQC-1tP-23@gated-at.bofh.it> <s56Ea-1t7-11@gated-at.bofh.it> <s57gS-25e-25@gated-at.bofh.it> <s57Tz-2lF-17@gated-at.bofh.it> <s5lDc-2Nj-29@gated-at.bofh.it> <s5lDc-2Nj-31@gated-at.bofh.it>
X-Ibm-Helo	d03dlp02.boulder.ibm.com
X-Ibm-Mailfrom	paulmck@linux.vnet.ibm.com
Reply-To	paulmck@linux.vnet.ibm.com
MIME-Version	1.0
Content-Type	text/plain; charset=us-ascii
Content-Disposition	inline
User-Agent	Mutt/1.5.21 (2010-09-15)
X-Tm-As-Gconf	00
X-Content-Scanned	Fidelis XPS MAILER
X-Cbid	16081216-0016-0000-0000-00000468505C
X-Ibm-Spammodules-Versions	BY=3.00005583; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000181; SDB=6.00743723; UDB=6.00350246; IPR=6.00516260; BA=6.00004660; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00012328; XFM=3.00000011; UTC=2016-08-12 16:19:25
X-Ibm-Av-Detection	SAVI=unused REMOTE=unused XFE=unused
X-Cbparentid	16081216-0017-0000-0000-000031F5967F
X-Proofpoint-Virus-Version	vendor=fsecure engine=2.50.10432:,, definitions=2016-08-12_07:,, signatures=0
X-Proofpoint-Spam-Details	rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1608120170
Sender	robomod@news.nic.it
List-ID	<linux-kernel.vger.kernel.org>
X-Mailing-List	linux-kernel@vger.kernel.org
Approved	robomod@news.nic.it
Lines	20
Organization	linux.* mail to news gateway
X-Original-Cc	Christoph Lameter <cl@linux.com>, Peter Zijlstra <peterz@infradead.org>, Chris Metcalf <cmetcalf@mellanox.com>, Gilad Ben Yossef <giladb@mellanox.com>, Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@kernel.org>, Andrew Morton <akpm@linux-foundation.org>, Rik van Riel <riel@redhat.com>, Tejun Heo <tj@kernel.org>, Thomas Gleixner <tglx@linutronix.de>, Viresh Kumar <viresh.kumar@linaro.org>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will.deacon@arm.com>, Andy Lutomirski <luto@amacapital.net>, Daniel Lezcano <daniel.lezcano@linaro.org>, linux-doc@vger.kernel.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
X-Original-Date	Fri, 12 Aug 2016 09:19:19 -0700
X-Original-Message-ID	<20160812161919.GV3482@linux.vnet.ibm.com>
X-Original-References	<7a3f66f7-5011-7d59-2e0e-f57e4e42e6b6@mellanox.com> <alpine.DEB.2.20.1607251133450.25354@east.gentwo.org> <alpine.DEB.2.20.1607270847460.24843@east.gentwo.org> <20160810221656.GC19757@lerouge> <20160811084002.GV30192@twins.programming.kicks-ass.net> <20160811160027.GV3482@linux.vnet.ibm.com> <alpine.DEB.2.20.1608111801320.8416@east.gentwo.org> <20160811234734.GJ3482@linux.vnet.ibm.com> <alpine.DEB.2.20.1608120922450.20310@east.gentwo.org> <20160812142611.GC5087@lerouge>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	csiph.com linux.kernel:1461304

Show key headers only | View raw

On Fri, Aug 12, 2016 at 04:26:13PM +0200, Frederic Weisbecker wrote:
> On Fri, Aug 12, 2016 at 09:23:13AM -0500, Christoph Lameter wrote:
> > On Thu, 11 Aug 2016, Paul E. McKenney wrote:
> > 
> > > Heh!  The only really good idea is for clocks to be reliably in sync.
> > >
> > > But if they go out of sync, what do you want to do instead?
> > 
> > For a NOHZ task? Write a message to the syslog and reenable tick.

Fair enough!  Kicking off a low-priority task would achieve the latter
but not necessarily the former.  And of course assumes that the worker
thread is at real-time priority with various scheduler anti-starvation
features disabled.

> Indeed, a strong clocksource is a requirement for a full tickless machine.

No disagrement here!  ;-)

							Thanx, Paul

Thread

Re: clocksource_watchdog causing scheduling of timers every second  (was [v13] support "task_isolation" mode) Frederic Weisbecker <fweisbec@gmail.com> - 2016-08-11 00:20 +0200
  Re: clocksource_watchdog causing scheduling of timers every second  (was [v13] support "task_isolation" mode) Peter Zijlstra <peterz@infradead.org> - 2016-08-11 10:50 +0200
    Re: clocksource_watchdog causing scheduling of timers every second  (was [v13] support "task_isolation" mode) Frederic Weisbecker <fweisbec@gmail.com> - 2016-08-11 14:10 +0200
    Re: clocksource_watchdog causing scheduling of timers every second  (was [v13] support "task_isolation" mode) "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-08-12 00:30 +0200
      Re: clocksource_watchdog causing scheduling of timers every second  (was [v13] support "task_isolation" mode) Christoph Lameter <cl@linux.com> - 2016-08-12 01:10 +0200
        Re: clocksource_watchdog causing scheduling of timers every second  (was [v13] support "task_isolation" mode) "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-08-12 01:50 +0200
          Re: clocksource_watchdog causing scheduling of timers every second  (was [v13] support "task_isolation" mode) Christoph Lameter <cl@linux.com> - 2016-08-12 16:30 +0200
            Re: clocksource_watchdog causing scheduling of timers every second  (was [v13] support "task_isolation" mode) Frederic Weisbecker <fweisbec@gmail.com> - 2016-08-12 16:30 +0200
              Re: clocksource_watchdog causing scheduling of timers every second  (was [v13] support "task_isolation" mode) "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-08-12 18:20 +0200
                Re: clocksource_watchdog causing scheduling of timers every second  (was [v13] support "task_isolation" mode) Frederic Weisbecker <fweisbec@gmail.com> - 2016-08-13 17:40 +0200

csiph-web