linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: "Antonios G. Danalis" <danalis@udel.edu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: increasing HZ in Linux kernel
Date: Fri, 14 Sep 2001 10:24:33 -0700	[thread overview]
Message-ID: <3BA23D51.B456C9EE@mvista.com> (raw)
In-Reply-To: <3BA134F3.FA661E9E@udel.edu>

"Antonios G. Danalis" wrote:
> 
> Hello,
> 
> I want to increase the frequency of the clock interrupt up
> to ~10000 to run some experiments.
> 
> In the kernel I'm using (2.4.2-2) I've noticed that
> if you increase HZ above 1536 you get a conflict with
> .../include/linux/timex.h:75-77
> and if you add some lines there, you get a problem with
> .../include/net/tcp.h:377
> when HZ is above 4096.
> 
> Is there an easy way to increase clock interrupt freq, or
> do I have to mess with the whole kernel ?
> 
The approach we are taking in the high-res-timers project
(http://sourceforge.net/projects/high-res-timers) is to leave HZ alone
and schedule timer interrupts as needed between the 1/HZ ticks.  I have
an kernel with most of the infrastructure ready to put on the
sourceforge site (today I hope), that you may want to look at.  Be
aware, however, it is not really a simple change.  You may also want to
look at the UTIME patch from the University of Kansas, which, to some
extent, is where I started.  We both leave HZ alone and schedule timer
ticks as needed to get high resolution.

As you have noted, changing HZ impacts other sub systems.  There is also
an issue of jiffie rollover which affects the longest time you can set
timers for.  Currently with HZ =100 and 32-bit integers, this is about
248.55 days.  If you move HZ to 1000, this moves to 24.855 days, and the
10,000 you want moves it to 2.4855 days which will give problems with at
least the cron sub system and probably a lot of others.

George

  reply	other threads:[~2001-09-14 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13 22:36 increasing HZ in Linux kernel Antonios G. Danalis
2001-09-14 17:24 ` george anzinger [this message]
2001-09-14 17:53   ` Frank Schneider
2001-09-15  7:15     ` george anzinger

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=3BA23D51.B456C9EE@mvista.com \
    --to=george@mvista.com \
    --cc=danalis@udel.edu \
    --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;
as well as URLs for NNTP newsgroup(s).