From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from penguin.netx4.com (embeddededge.com [209.113.146.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 692DC680A4 for ; Sun, 28 Aug 2005 10:48:29 +1000 (EST) In-Reply-To: <20050827050422.GC7234@siegfried.thelikelysolution.ca> References: <20050826225509.GF5541@smtp.west.cox.net> <20050827050422.GC7234@siegfried.thelikelysolution.ca> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: From: Dan Malek Date: Sat, 27 Aug 2005 20:48:04 -0400 To: Grant Likely Cc: Andrew Morton , Tom Rini , Kumar Gala , linuxppc-dev@ozlabs.org Subject: Re: [PATCH] ppc32: add CONFIG_HZ List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Aug 27, 2005, at 1:04 AM, Grant Likely wrote: > What's the reason for clock jitter? Is it because most timeouts are > set > to multiples of 100, or some other reason? Yes, the application interfaces are all defined as 100 Hz (10 mSec). If the POSIX timer implementation is done properly, it should be possible to determine the timer parameters to eliminate this, but I doubt any applications do this. They all assume 10 mSec :-) -- Dan