From: Thomas Gleixner <tglx@linutronix.de>
To: Dimitri Sivanich <sivanich@sgi.com>
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 18:39:19 +0200 [thread overview]
Message-ID: <1158338360.5724.442.camel@localhost.localdomain> (raw)
In-Reply-To: <20060914132917.GA9898@sgi.com>
On Thu, 2006-09-14 at 08:29 -0500, Dimitri Sivanich wrote:
> This patch allows the user to migrate currently queued
> standard timers from one cpu to another, thereby reducing
> timer induced latency on the chosen cpu. Timers that
> were placed with add_timer_on() are considered to have
> 'cpu affinity' and are not moved.
>
> The changes in drivers/base/cpu.c provide a clean and
> convenient interface for triggering the migration through
> sysfs, via writing the destination cpu number to a file
> associated with the source cpu.
>
> Note that migrating timers will not, by itself, keep new
> timers off of the chosen cpu. But with careful control of
> thread affinity, one can control the affinity of new timers
> and keep timer induced latencies off of the chosen cpu.
>
> This particular patch does not affect the hrtimers. That
> could be addressed later.
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.
tglx
next prev parent reply other threads:[~2006-09-15 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 13:29 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 [this message]
2006-09-15 16:58 ` Dimitri Sivanich
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=1158338360.5724.442.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sivanich@sgi.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
Powered by JetHome