From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262929AbVGNUmX (ORCPT ); Thu, 14 Jul 2005 16:42:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263064AbVGNUmX (ORCPT ); Thu, 14 Jul 2005 16:42:23 -0400 Received: from graphe.net ([209.204.138.32]:57217 "EHLO graphe.net") by vger.kernel.org with ESMTP id S262929AbVGNUmQ (ORCPT ); Thu, 14 Jul 2005 16:42:16 -0400 Date: Thu, 14 Jul 2005 13:41:44 -0700 (PDT) From: Christoph Lameter X-X-Sender: christoph@graphe.net To: Linus Torvalds cc: john stultz , Arjan van de Ven , Vojtech Pavlik , Lee Revell , dean gaudet , Chris Wedgwood , Andrew Morton , Len Brown , dtor_core@ameritech.net, david.lang@digitalinsight.com, davidsen@tmr.com, kernel@kolivas.org, lkml , mbligh@mbligh.org, diegocg@gmail.com, azarah@nosferatu.za.org Subject: Re: [PATCH] i386: Selectable Frequency of the Timer Interrupt In-Reply-To: Message-ID: References: <1121286258.4435.98.camel@mindpipe> <20050713134857.354e697c.akpm@osdl.org> <20050713211650.GA12127@taniwha.stupidest.org> <20050714005106.GA16085@taniwha.stupidest.org> <1121304825.4435.126.camel@mindpipe> <1121326938.3967.12.camel@laptopd505.fenrus.org> <20050714121340.GA1072@ucw.cz> <1121360561.3967.55.camel@laptopd505.fenrus.org> <1121370122.7673.161.camel@cog.beaverton.ibm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: -5.9 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 14 Jul 2005, Linus Torvalds wrote: > So the _sane_ way to do timeouts is to define an _arbitrary_ clock that is > just an integer counter. None of this "nanoseconds + full seconds" crap. > None of this stupid confusion with "real time". You select something that > is conceptually _clearly_ somethign else, and that will never get confused > when root sets the time backwards or anything like that. > > In other words, you select the thing we call "jiffies". AFAIK John simply wants to change jiffies to count in nanoseconds since bootup and then call it "clock_monotonic". One 64 bit value no splitting into seconds and nanoseconds anymore. This allows arbitrary length intervals between timer interrupts.