From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753850AbcFQO0L (ORCPT ); Fri, 17 Jun 2016 10:26:11 -0400 Received: from mail-yw0-f171.google.com ([209.85.161.171]:33064 "EHLO mail-yw0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752024AbcFQO0J (ORCPT ); Fri, 17 Jun 2016 10:26:09 -0400 MIME-Version: 1.0 In-Reply-To: <20160617121134.417319325@linutronix.de> References: <20160617121134.417319325@linutronix.de> From: Arjan van de Ven Date: Fri, 17 Jun 2016 07:26:08 -0700 Message-ID: Subject: Re: [patch V2 00/20] timer: Refactor the timer wheel To: Thomas Gleixner Cc: LKML , Ingo Molnar , Peter Zijlstra , "Paul E. McKenney" , Eric Dumazet , Frederic Weisbecker , Chris Mason , Arjan van de Ven , rt@linutronix.de, Rik van Riel , Linus Torvalds , George Spelvin , Len Brown Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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)