[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1466449437.2756.41.camel@redhat.com>
Date: Mon, 20 Jun 2016 15:03:57 -0400
From: Rik van Riel <riel@...hat.com>
To: Thomas Gleixner <tglx@...utronix.de>,
Eric Dumazet <edumazet@...gle.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Chris Mason <clm@...com>,
Arjan van de Ven <arjan@...radead.org>, rt@...utronix.de,
Linus Torvalds <torvalds@...ux-foundation.org>,
George Spelvin <linux@...encehorizons.net>,
Len Brown <lenb@...nel.org>
Subject: Re: [patch V2 00/20] timer: Refactor the timer wheel
On Mon, 2016-06-20 at 15:56 +0200, 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.
>
It might be easy enough to simply re-queue a timer that
has not expired yet after 37 hours.
How many 37 hour timers will there be outstanding at any
one time, that expire around the same time?
Chances are, not many at all. In fact, the vast majority
of them are likely to be deleted long before they ever
expire.
Timers lasting longer than 37 hours do not seem like
something worth optimizing for.
--
All Rights Reversed.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists