All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Stas Sergeev <stsp@aknet.ru>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [rfc][patch] API for timer hooks
Date: Thu, 18 Aug 2005 13:07:15 -0400	[thread overview]
Message-ID: <1124384836.5973.16.camel@mindpipe> (raw)
In-Reply-To: <4304BE76.5090003@aknet.ru>

On Thu, 2005-08-18 at 20:59 +0400, Stas Sergeev wrote:
> The only limitation would be that when the
> speaker driver is enabled in the config,
> the ability to manually select the CONFIG_HZ
> will be lost, but maybe it is not that bad
> at all 

CONFIG_HZ is just a short term hack to placate people who insist on a
tick rate lower than 1000 but can't wait for dynamic tick to be ready.
Once dynamic tick is merged then CONFIG_HZ will need to go away.  We
don't impose arbitrary restrictions on the period of the soundcard
interrupt, I don't see why the PIT should be any different.

I would be quite disappointed if dynamic tick does not get merged for
2.6.14.

Lee



      reply	other threads:[~2005-08-18 17:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-13 13:36 [rfc][patch] API for timer hooks Stas Sergeev
2005-08-15 17:19 ` john stultz
2005-08-16 20:21   ` Stas Sergeev
2005-08-16 22:24     ` Nish Aravamudan
2005-08-17 16:10       ` Stas Sergeev
2005-08-17  2:09     ` Lee Revell
2005-08-17 16:21       ` Stas Sergeev
2005-08-17 16:40         ` Lee Revell
2005-08-17 17:41           ` Stas Sergeev
2005-08-17 23:16             ` Lee Revell
2005-08-18 16:59               ` Stas Sergeev
2005-08-18 17:07                 ` Lee Revell [this message]

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=1124384836.5973.16.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stsp@aknet.ru \
    /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.