From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755371AbcFTOtF (ORCPT ); Mon, 20 Jun 2016 10:49:05 -0400 Received: from www.linutronix.de ([62.245.132.108]:60383 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755317AbcFTOs0 (ORCPT ); Mon, 20 Jun 2016 10:48:26 -0400 Date: Mon, 20 Jun 2016 16:46:23 +0200 (CEST) From: Thomas Gleixner To: Arjan van de Ven cc: Eric Dumazet , LKML , Ingo Molnar , Peter Zijlstra , "Paul E. McKenney" , Frederic Weisbecker , Chris Mason , Arjan van de Ven , rt@linutronix.de, Rik van Riel , Linus Torvalds , George Spelvin , Len Brown Subject: Re: [patch V2 00/20] timer: Refactor the timer wheel In-Reply-To: Message-ID: References: <20160617121134.417319325@linutronix.de> 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,URIBL_BLOCKED=0.001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 20 Jun 2016, Arjan van de Ven wrote: > On Mon, Jun 20, 2016 at 6:56 AM, Thomas Gleixner wrote: > > > > 2) Cut off at 37hrs for HZ=1000. We could make this configurable as a 1000HZ > > option so datacenter folks can use this and people who don't care and want > > better batching for power can use the 4ms thingy. > > > if there really is one user of such long timers... could we possibly > make that one robust against early fire of the timer? > > eg rule is: if you set timers > 37 hours, you need to cope with early timer fire The only user I found is networking contrack (5 days). Eric thought its not a big problem if it fires earlier. Thanks, tglx