Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760805AbXHHLBU (ORCPT ); Wed, 8 Aug 2007 07:01:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751045AbXHHLBK (ORCPT ); Wed, 8 Aug 2007 07:01:10 -0400 Received: from ns2.suse.de ([195.135.220.15]:52846 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750734AbXHHLBJ (ORCPT ); Wed, 8 Aug 2007 07:01:09 -0400 To: Andrew Morton Cc: Jonathan Corbet , linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , Roman Zippel Subject: Re: [PATCH] msleep() with hrtimers References: <15327.1186166232@lwn.net> <20070807124009.9f6c2247.akpm@linux-foundation.org> From: Andi Kleen Date: 08 Aug 2007 13:55:28 +0200 In-Reply-To: <20070807124009.9f6c2247.akpm@linux-foundation.org> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 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: 664 Lines: 13 Andrew Morton writes: > > I'd be surprised if there was significant overhead - the maximum frequency > at which msleep() can be called is 1000Hz. We'd need an awful lot of > overhead for that to cause problems, surely? The bigger risk is probably to break drivers that rely on msleep(1) really being msleep( very long depending on HZ ) But the only way to find out is to try it. -Andi - 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/