From: ebiederm@xmission.com (Eric W. Biederman)
To: Andre Hedrick <andre@linux-ide.org>
Cc: george anzinger <george@mvista.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org,
high-res-timers-discourse@lists.sourceforge.net
Subject: Re: Linux-Kernel Archive: No 100 HZ timer !
Date: 13 Apr 2001 01:21:39 -0600 [thread overview]
Message-ID: <m1snjdtgcc.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10104122102170.4564-100000@master.linux-ide.org>
In-Reply-To: Andre Hedrick's message of "Thu, 12 Apr 2001 21:04:28 -0700 (PDT)"
Andre Hedrick <andre@linux-ide.org> writes:
> On Thu, 12 Apr 2001, george anzinger wrote:
>
> > Actually we could do the same thing they did for errno, i.e.
> >
> > #define jiffies get_jiffies()
> > extern unsigned get_jiffies(void);
>
> > No, not really. HZ still defines the units of jiffies and most all the
> > timing is still related to it. Its just that interrupts are only "set
> > up" when a "real" time event is due.
>
> Great HZ always defines units of jiffies, but that is worthless if there
> is not a ruleset that tells me a value to divide by to return it to a
> specific quantity of time.
Actually in rearranging it. jiffies should probably be redefined as
the smallest sleep we are prepared to take. And then HZ because the
number of those smallest sleeps per second. So we might see HZ values
up in the millions but otherwise things should be pretty much as
normal.
It's an interesting question though. How large should HZ be with
programmable timers.
Eric
next prev parent reply other threads:[~2001-04-13 7:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3AD622AB.5F0A061B@linux-ide.org>
2001-04-12 21:52 ` Linux-Kernel Archive: No 100 HZ timer ! Andre Hedrick
2001-04-12 23:12 ` Alan Cox
2001-04-12 23:21 ` Andre Hedrick
2001-04-13 2:58 ` george anzinger
2001-04-13 4:04 ` Andre Hedrick
2001-04-13 7:21 ` Eric W. Biederman [this message]
2001-04-13 8:28 ` george anzinger
2001-04-13 12:20 ` Mark Salisbury
2001-04-13 12:55 ` Michael Raymond
2001-04-13 15:50 ` george anzinger
2001-04-13 9:05 ` David Schleef
2001-04-13 12:47 ` Alan Cox
2001-04-14 13:57 ` Rogier Wolff
2001-04-15 2:10 ` Roger Larsson
2001-04-15 7:22 ` george anzinger
2001-04-16 15:32 ` Pavel Machek
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=m1snjdtgcc.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=george@mvista.com \
--cc=high-res-timers-discourse@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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