public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christopher Friesen" <cfriesen@nortel.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Con Kolivas <kernel@kolivas.org>
Subject: Re: Dynamic tick for 2.6.14 - what's the plan?
Date: Mon, 29 Aug 2005 16:42:03 -0600	[thread overview]
Message-ID: <43138F3B.7010704@nortel.com> (raw)
In-Reply-To: <1125354385.4598.79.camel@mindpipe>

Lee Revell wrote:
> The controversy over the introduction of CONFIG_HZ demonstrated the
> urgency of getting a dynamic tick solution merged before 2.6.14.
> 
> Anyone care to give a status report?  Con, do you feel that the last
> version you posted is ready to go in?

Last time I got interested in this, the management of the event queues 
was still a fairly major performance hit.

Has this overhead been brought down to reasonable levels?

Chris

  reply	other threads:[~2005-08-29 22:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29 22:26 Dynamic tick for 2.6.14 - what's the plan? Lee Revell
2005-08-29 22:42 ` Christopher Friesen [this message]
2005-08-30  0:05   ` Con Kolivas
2005-08-30  2:54     ` Theodore Ts'o
2005-08-30  3:48       ` Con Kolivas
2005-08-30 12:31         ` Tony Lindgren
2005-08-30 16:01           ` Alistair John Strachan
2005-08-31  7:44             ` Tony Lindgren
2005-08-31  8:39               ` Arjan van de Ven
2005-08-31 10:34                 ` Tony Lindgren
2005-08-31 10:50                   ` Srivatsa Vaddagiri
2005-08-31 11:03                   ` Arjan van de Ven
2005-08-31 11:17                     ` Srivatsa Vaddagiri
2005-08-31 11:20                       ` Srivatsa Vaddagiri
2005-08-31 13:21                         ` Tony Lindgren
2005-09-01  6:36                           ` Tony Lindgren
2005-08-31 17:39   ` Srivatsa Vaddagiri
2005-08-31 17:42     ` Christopher Friesen

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=43138F3B.7010704@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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