public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@xs4all.nl>
To: Rob Love <rml@ximian.com>
Cc: Arjan van de Ven <arjanv@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.23 can run with HZ==0!
Date: Mon, 29 Dec 2003 16:54:33 +0100	[thread overview]
Message-ID: <20031229155433.GA4475@janus> (raw)
In-Reply-To: <1072711585.4294.8.camel@fur>

On Mon, Dec 29, 2003 at 10:26:25AM -0500, Rob Love wrote:
> On Mon, 2003-12-29 at 07:52, Frank van Maarseveen wrote:
> 
> > Can you give me an example?
> 
> Sure, as this has already been done:
> 
> 	http://www.kernel.org/pub/linux/kernel/people/rml/variable-HZ/v2.4/

That looks more complete and its cleaner. When I needed the HZ patch I
deliberately didn't care about #ifdef __KERNEL__ in the header files. It
was a tmp hack anyway.

it doesn't contain the #if HZ==1000 fix in timer.c. I'm not sure if it
is that important and this one is broke since it fixes yet another HZ
value instead of all.

> 
> As you see, that has a ton of fixups, primarily to ensure that
> user-space is always exported jiffies in terms of USER_HZ==100.

I missed a two or three cases. Hoever, no sign of the tenfold size increase
or any fixes inside SCSI ioctls or firewall rules (netfilter code I presume).

Arjan, are you sure?

-- 
Frank

  reply	other threads:[~2003-12-29 15:50 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
2003-12-29 15:26     ` Rob Love
2003-12-29 15:54       ` Frank van Maarseveen [this message]
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=20031229155433.GA4475@janus \
    --to=frankvm@xs4all.nl \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@ximian.com \
    /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