public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert de Bath <robert$@mayday.cix.co.uk>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
	Tim Schmielau <tim@physik3.uni-rostock.de>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH *] use 64 bit jiffies
Date: Tue, 4 Feb 2003 08:27:38 +0000 (GMT)	[thread overview]
Message-ID: <6789aaded8e91844@mayday.cix.co.uk> (raw)
In-Reply-To: <200302040643.h146gps10473@Port.imtp.ilyichevsk.odessa.ua>


On Tue, 4 Feb 2003, Denis Vlasenko wrote:

> 		Jiffy Wrap Bugs
>
> There were reports of machines hanging on jiffy wrap.
> This is typically a result of incorrect jiffy use in some driver.
> Ask Tim - he is hunting those problems regularly, but he is outnumbered
> by buggy driver authors. :(
>
> There is a better solution to ensure correct jiffy wrap handling in
> *ALL* kernel code: make jiffy wrap in first five minutes of uptime.
> Tim has a patch for such config option. This is almost right.
> This MUST NOT be a config option, it MUST be mandatory in every
> kernel. Driver writers would be bitten by their own bugs and will
> fix it themself. Tim, what do you think?

How about an option, either the jiffy timer wraps at 5 minutes or
process 1 gets sent a SIGINT after 24 hours ? That way a driver
with an MIA author can still be used even if it's buggy, just not
for very long.

Okay ... perhaps it should be just an option of jiffy wrap at 5 mins
or 24 hours, but I still think reboot is better :-) :-P

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>
Google Homepage:   http://www.google.com/search?btnI&q=Robert+de+Bath


  reply	other threads:[~2003-02-04  8:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 22:55 [PATCH *] use 64 bit jiffies Tim Schmielau
2003-02-03  6:42 ` Denis Vlasenko
2003-02-03  8:28   ` Matti Aarnio
2003-02-03  8:47     ` Tim Schmielau
2003-02-03  8:55       ` Matti Aarnio
2003-02-04 13:00         ` Tim Schmielau
2003-02-04  6:41     ` Denis Vlasenko
2003-02-04  8:27       ` Robert de Bath [this message]
2003-02-04  8:41         ` Denis Vlasenko
2003-02-04  9:29       ` Jörn Engel
2003-02-04 13:04         ` Tim Schmielau
2003-02-17 13:55           ` Jörn Engel
2003-02-17 14:02             ` Tim Schmielau
2003-02-17 14:15             ` Matti Aarnio
2003-02-17 14:23               ` Tim Schmielau
2003-02-04 17:37       ` Randy.Dunlap
2003-02-16  1:37         ` [PATCH] make jiffies wrap 5 min after boot Tim Schmielau
2003-02-16  2:08           ` Anton Blanchard
2003-02-16  2:43             ` William Lee Irwin III
2003-02-16  2:50               ` Michael Vergoz
2003-02-16  6:37               ` Robert Love
2003-02-16  7:16                 ` Muli Ben-Yehuda
2003-02-16 11:50                   ` Falk Hueffner
2003-02-16 12:04                     ` William Lee Irwin III
2003-02-11 20:50       ` [patch] jiffies wrap fixes for 2.5.60 Tim Schmielau
2003-02-11 21:31         ` Roger Larsson
2003-02-12 12:09           ` Tim Schmielau
2003-02-05 11:42 ` use 64 bit jiffies broke HZ=100 case (and fix) Oleg Drokin
2003-02-05 12:22   ` Tim Schmielau

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=6789aaded8e91844@mayday.cix.co.uk \
    --to=robert$@mayday.cix.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=tim@physik3.uni-rostock.de \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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