public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dimitri Sivanich <sivanich@sgi.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, Andi Kleen <ak@suse.de>
Subject: Re: [PATCH] Migration of standard timers
Date: Fri, 15 Sep 2006 11:58:10 -0500	[thread overview]
Message-ID: <20060915165810.GA3832@sgi.com> (raw)
In-Reply-To: <1158338360.5724.442.camel@localhost.localdomain>

On Fri, Sep 15, 2006 at 06:39:19PM +0200, Thomas Gleixner wrote:
> Are you trying to work around the latencies caused by long running timer
> callbacks ? I'm not convinced that this is not curing the symptoms
> instead of the root cause.

Yes, both latency from long running timer callbacks as well as
potential latency from a temporal grouping of timer callbacks
(those occuring on the same tick).

While I agree that root causes of the former should be addressed,
more latencies of this type can always easily creep in.  Timer
migration works as a long term preventative aid, not just a fix
for the problem of the moment.  And adding this needn't restrict
anyone from looking at the aforementioned root causes.

  reply	other threads:[~2006-09-15 16:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 13:29 [PATCH] Migration of standard timers Dimitri Sivanich
2006-09-14 14:11 ` Jes Sorensen
2006-09-14 14:30   ` Dimitri Sivanich
2006-09-15  6:06 ` Andrew Morton
2006-09-15 16:39 ` Thomas Gleixner
2006-09-15 16:58   ` Dimitri Sivanich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-19 15:29 [PATCH] Migration of Standard Timers Dimitri Sivanich
2006-09-19 16:33 ` Lee Revell
2006-09-19 16:41   ` Dimitri Sivanich
2006-09-19 16:57     ` Lee Revell
2006-09-22 19:16 ` Andrew Morton

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=20060915165810.GA3832@sgi.com \
    --to=sivanich@sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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