Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 18 Feb 2002 16:57:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 18 Feb 2002 16:57:25 -0500 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:64008 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Mon, 18 Feb 2002 16:57:12 -0500 Subject: Re: jiffies rollover, uptime etc. To: oh@novaville.de (Oliver Hillmann) Date: Mon, 18 Feb 2002 22:10:56 +0000 (GMT) Cc: linux-kernel@vger.kernel.org In-Reply-To: from "Oliver Hillmann" at Feb 18, 2002 10:42:50 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > counter, and I'm currently digging into that area... Stuff like a pc > speaker driver going wild bothers me a bit more... Fix the speaker driver I guess is the answer. It shouldnt have done that. > Could anybody perhaps tell me why he/she doesn't consider this a > problem? And is there a fundamental problem with solving this in > general? (I do see a problem with defining jiffies long long on x86, > because it might break a lot of things and probably wouldnt perform > as often as jiffies is touched... And you might sense I haven't > been into kernel hacking much...) Counting in long long is expensive and the drivers are meant to all use roll over safe compares - 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/