Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762114AbXHCTT3 (ORCPT ); Fri, 3 Aug 2007 15:19:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758267AbXHCTTW (ORCPT ); Fri, 3 Aug 2007 15:19:22 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:3377 "EHLO scrub.xs4all.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757736AbXHCTTW (ORCPT ); Fri, 3 Aug 2007 15:19:22 -0400 Date: Fri, 3 Aug 2007 21:19:36 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Jonathan Corbet cc: linux-kernel@vger.kernel.org, Thomas Gleixner , akpm@linux-foundation.org, Ingo Molnar Subject: Re: [PATCH] msleep() with hrtimers In-Reply-To: <15327.1186166232@lwn.net> Message-ID: References: <15327.1186166232@lwn.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 999 Lines: 22 Hi, On Fri, 3 Aug 2007, Jonathan Corbet wrote: > Most comments last time were favorable. The one dissenter was Roman, > who worries about the overhead of using hrtimers for this operation; my > understanding is that he would rather see a really_msleep() function for > those who actually want millisecond resolution. I'm not sure how to > characterize what the cost could be, but it can only be buried by the > fact that every call sleeps for some number of milliseconds. On my > system, the several hundred total msleep() calls can't cause any real > overhead, and almost all happen at initialization time. The main point is still that these are two _different_ APIs for different usages, so I still prefer to add a hrsleep() instead. bye, Roman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/