All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: linux-kernel@vger.kernel.org
Subject: Re: HZ question
Date: Tue, 13 Sep 2005 15:17:55 -0400	[thread overview]
Message-ID: <432725E3.70304@compro.net> (raw)
In-Reply-To: <43271CA3.7050706@stesmi.com>

Stefan Smietanowski wrote:
> Mark Hounschell wrote:
>>>Tim Schmielau wrote:
>>>
>>>>Do you also want to know about CONFIG_PREEMPT, SMP, current load, future
>>>>load in order to estimate the delay you want to ask for?
>>>
>>>Are not CONFIG_PREEMPT, SMP, and current load, all determinable from
>>>userland anyway? Why not HZ?
> 
> And with dynamic HZ?
> 
> Do you want
> a) The HZ that was used when we booted
> b) The HZ that is currently used (say 22, but could be 573 in 0.1s)
> c) The MIN HZ (if there is such a thing and it is configured)
>    that the kernel will use.
> d) The MAX HZ (same) that the kernel will use.
> 
> Or do you want USER_HZ?
> 
> Or are you after something else entirely.
> 
> // Stefan

If dynamic HZ means dynamic timer resolutions I don't want it at all.

I guess the 'terms' John just used, ie timer resolutions, as opposed to
HZ was maybe what I really should have asked for to begin with.

However since they are both bascially the same or at least one derived
from the other......?

Thanks
Mark

  reply	other threads:[~2005-09-13 19:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 12:48 HZ question Mark Hounschell
2005-09-13 13:46 ` linux-os (Dick Johnson)
2005-09-13 14:00   ` Mark Hounschell
2005-09-13 14:20     ` Tim Schmielau
2005-09-13 15:05       ` Mark Hounschell
2005-09-13 16:01         ` Tim Schmielau
2005-09-13 16:41           ` Mark Hounschell
2005-09-13 16:47           ` Mark Hounschell
2005-09-13 18:38             ` Stefan Smietanowski
2005-09-13 19:17               ` Mark Hounschell [this message]
2005-09-13 23:19                 ` Daniel Barkalow
2005-09-13 17:34         ` john stultz
2005-09-13 19:15           ` Mark Hounschell
2005-09-14  4:15           ` George Anzinger
2005-09-13 20:13   ` jdow
2005-09-13 20:38     ` linux-os (Dick Johnson)
2005-09-15  1:29       ` Lee Revell
2005-09-13 14:07 ` Tim Schmielau
2005-09-14  4:00 ` Coywolf Qi Hunt
2005-09-15  1:20   ` Lee Revell
2005-09-15 16:16     ` Joe Bob Spamtest
2005-09-15 20:19       ` Valdis.Kletnieks
2005-09-15 20:34         ` Jesper Juhl

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=432725E3.70304@compro.net \
    --to=markh@compro.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.