public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Oliver Hillmann <oh@novaville.de>, linux-kernel@vger.kernel.org
Subject: Re: jiffies rollover, uptime etc.
Date: Mon, 18 Feb 2002 15:19:22 -0700	[thread overview]
Message-ID: <3C717DEA.7090309@candelatech.com> (raw)
In-Reply-To: <E16cvzs-0006y2-00@the-village.bc.nu>



Alan Cox wrote:

>>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


I wonder, is it more expensive to write all drivers to handle the
wraps than to take the long long increment hit?  The increment is
once every 10 miliseconds, right?  That is not too often, all things
considered...

Maybe the non-atomicity of the long long increment is the problem?

Does this problem still exist on 64-bit machines?

THanks,
Ben



-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



  parent reply	other threads:[~2002-02-18 22:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-18 21:42 jiffies rollover, uptime etc Oliver Hillmann
2002-02-18 22:10 ` Alan Cox
2002-02-18 22:03   ` Oliver Hillmann
2002-02-18 22:19   ` Ben Greear [this message]
2002-02-18 22:32     ` Tim Schmielau
2002-02-18 22:43     ` Alan Cox
2002-02-18 23:26       ` bert hubert
2002-02-18 23:56         ` J Sloan
2002-02-18 23:57         ` Alan Cox
2002-02-19  0:58         ` Stephen Frost
2002-02-19  4:47           ` Paul Jakma
2002-02-19  0:17     ` Bill Davidsen
2002-02-19 20:55       ` george anzinger
2002-02-20 11:36         ` Ville Herva
2002-02-20 17:20           ` Mike Fedyk
2002-02-20 17:24             ` Rik van Riel
2002-02-20 17:32               ` Mike Fedyk
2002-02-20 17:39                 ` Rik van Riel
2002-02-20 17:44                   ` Mike Fedyk
2002-02-20 17:56                 ` Derek Gladding
2002-02-21 13:19                 ` Bill Davidsen
2002-02-20 19:08               ` David Mosberger
2002-02-20 19:53               ` Robert Love
2002-02-20 15:46         ` Bill Davidsen
2002-02-20 16:50           ` george anzinger
2002-02-18 22:12 ` Tim Schmielau
2002-02-18 23:22   ` J Sloan
  -- strict thread matches above, loose matches on Subject: below --
2002-02-19  2:54 Chris Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C717DEA.7090309@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oh@novaville.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox