From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932202AbcFNSHw (ORCPT <rfc822;w@1wt.eu>);
	Tue, 14 Jun 2016 14:07:52 -0400
Received: from www.linutronix.de ([62.245.132.108]:35838 "EHLO
	Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752502AbcFNSHv (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 14 Jun 2016 14:07:51 -0400
Date: Tue, 14 Jun 2016 20:05:49 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: Arjan van de Ven <arjanvandeven@gmail.com>
cc: Ingo Molnar <mingo@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
        LKML <linux-kernel@vger.kernel.org>,
        "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
        Eric Dumazet <edumazet@google.com>,
        Frederic Weisbecker <fweisbec@gmail.com>, Chris Mason <clm@fb.com>,
        Arjan van de Ven <arjan@infradead.org>, rt@linutronix.de,
        Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch 13/20] timer: Switch to a non cascading wheel
In-Reply-To: <CADyApD1L48AVT7D94wYuL89m7V+--rg59GFvHzhHMZ5uhhdaYw@mail.gmail.com>
Message-ID: <alpine.DEB.2.11.1606142000150.5839@nanos>
References: <20160613070440.950649741@linutronix.de> <20160613075929.282143900@linutronix.de> <20160613114005.GY30909@twins.programming.kicks-ass.net> <alpine.DEB.2.11.1606131426330.5839@nanos> <20160614101144.GA849@gmail.com> <alpine.DEB.2.11.1606141213300.5839@nanos>
 <CADyApD1L48AVT7D94wYuL89m7V+--rg59GFvHzhHMZ5uhhdaYw@mail.gmail.com>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Linutronix-Spam-Score: -1.0
X-Linutronix-Spam-Level: -
X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required,  ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 14 Jun 2016, Arjan van de Ven wrote:

> evaluating a 120 hours timer ever 37 hours to see if it should fire...
> not too horrid.

Well that thing is doing weird stuff anyway:

   swapper     0 [001] 1789995.305532: timer:timer_start: timer=0xffff8800c8346920 function=death_by_timeout expires=4850639994 [timeout=108000000]
             ssh  3870 [001] 1790025.284704: timer:timer_cancel: timer=0xffff8800c8346920
             ssh  3870 [001] 1790025.284707: timer:timer_start: timer=0xffff8800c8346920 function=death_by_timeout expires=4742722493 [timeout=75000]
         swapper     0 [001] 1790025.330514: timer:timer_cancel: timer=0xffff8800c8346920
         swapper     0 [001] 1790025.330515: timer:timer_start: timer=0xffff8800c8346920 function=death_by_timeout expires=4850647504 [timeout=108000000]
             ssh  3870 [001] 1790055.307058: timer:timer_cancel: timer=0xffff8800c8346920
             ssh  3870 [001] 1790055.307060: timer:timer_start: timer=0xffff8800c8346920 function=death_by_timeout expires=4742730003 [timeout=75000]
         swapper     0 [001] 1790055.352146: timer:timer_cancel: timer=0xffff8800c8346920

And that goes on forever. 2834 such sequences for this particular timer
instance in 4.5 hours. 90000 sequences total for all timers related to
death_by_timeout in 4.5 hours

No idea what this is doing and why the heck it nees a 120 hour timeout ....

Thanks,

	tglx