From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261335AbVGWL4f (ORCPT ); Sat, 23 Jul 2005 07:56:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261350AbVGWL4d (ORCPT ); Sat, 23 Jul 2005 07:56:33 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:10413 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S261335AbVGWL4c (ORCPT ); Sat, 23 Jul 2005 07:56:32 -0400 Date: Sat, 23 Jul 2005 13:55:58 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Arjan van de Ven cc: Nishanth Aravamudan , Andrew Morton , domen@coderock.org, linux-kernel@vger.kernel.org, clucas@rotomalug.org Subject: Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces In-Reply-To: <1122116986.3582.7.camel@localhost.localdomain> Message-ID: References: <20050707213138.184888000@homer> <20050708160824.10d4b606.akpm@osdl.org> <20050723002658.GA4183@us.ibm.com> <1122078715.5734.15.camel@localhost.localdomain> <1122116986.3582.7.camel@localhost.localdomain> 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 Hi, On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > What's wrong with using jiffies? > > A lot of the (driver) users want a wallclock based timeout. For that, > miliseconds is a more obvious API with less chance to get the jiffies/HZ > conversion wrong by the driver writer. We have helper functions for that. The point about using jiffies is to make it _very_ clear, that the timeout is imprecise and for most users this is sufficient. bye, Roman