[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADyApD2uUOasqiiX4Tvsqqpg6M0yhaFr_tmGn0pcT1OsRJqq8Q@mail.gmail.com>
Date: Fri, 17 Jun 2016 07:26:08 -0700
From: Arjan van de Ven <arjanvandeven@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
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>,
Eric Dumazet <edumazet@...gle.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Chris Mason <clm@...com>,
Arjan van de Ven <arjan@...radead.org>, rt@...utronix.de,
Rik van Riel <riel@...hat.com>,
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
> To achieve this capacity with HZ=1000 without increasing the storage size
> by another level, we reduced the granularity of the first wheel level from
> 1ms to 4ms. According to our data, there is no user which relies on that
> 1ms granularity and 99% of those timers are canceled before expiry.
the only likely problem cases are msleep(1) uses... but we could just
map those to usleep(1000,2000)
(imo we should anyway)
Powered by blists - more mailing lists