public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Frank van Maarseveen <frankvm@xs4all.nl>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.23 can run with HZ==0!
Date: Mon, 29 Dec 2003 13:52:56 +0100	[thread overview]
Message-ID: <20031229125256.GA28065@devserv.devel.redhat.com> (raw)
In-Reply-To: <20031229125240.GA4055@janus>

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]

On Mon, Dec 29, 2003 at 01:52:40PM +0100, Frank van Maarseveen wrote:
> On Mon, Dec 29, 2003 at 10:45:27AM +0100, Arjan van de Ven wrote:
> > 
> > not all motherboards can deal with HZ=1000.... seems yours is one of
> > thise.
> 
> But it seems to work. I would expect it to fail quite soon right at or after
> boot, not after a day once every few weeks (assuming it was the cause).
> 
> > your patch is *highly* inadequate to get HZ=1000 working well in 2.4....
> > it needs to be about 10x bigger with fixing more userspace api's...
> 
> Can you give me an example?
> 
> HZ for x386 is 100 by definition and there aren't that many system calls
> and /proc files which expose jiffies to userspace.

there are quite a few you missed; scsi ioctls is one, firewall rules are
another.... there's a long list (2.6 has most if not all of them fixed)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-12-29 12:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-28 23:05 2.4.23 can run with HZ==0! Frank van Maarseveen
2003-12-29  9:45 ` Arjan van de Ven
2003-12-29 12:52   ` Frank van Maarseveen
2003-12-29 12:52     ` Arjan van de Ven [this message]
2003-12-29 15:26     ` Rob Love
2003-12-29 15:54       ` Frank van Maarseveen
2003-12-29 15:54         ` Arjan van de Ven
2003-12-29 16:05         ` Rob Love

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=20031229125256.GA28065@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=frankvm@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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