From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: arun@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, ego@in.ibm.com,
tglx@linutronix.de, mingo@elte.hu, andi@firstfloor.org,
venkatesh.pallipadi@intel.com, vatsa@linux.vnet.ibm.com
Subject: Re: [RFC PATCH 0/1]: timers: Timer Migration
Date: Tue, 16 Sep 2008 14:05:30 +0200 [thread overview]
Message-ID: <1221566730.6943.16.camel@lappy.programming.kicks-ass.net> (raw)
In-Reply-To: <20080916091219.GA1068@linux.vnet.ibm.com>
On Tue, 2008-09-16 at 14:42 +0530, Arun R Bharadwaj wrote:
> Hi,
80 char lines please.
> An idle cpu on which device drivers have initialized timers, has to be
> frequently woken up to service the timers. So, consolidation of timers
> onto a fewer number of cpus is important. Migration of
> timers from idle cpus onto lesser idle cpus is necessary. Currently,
> timers are migrated during the cpu offline operation. However
> cpu-hotplug for the sake of idle system power management is too
> heavy. So, this patch implements a lightweight timer migration
> framework.
>
> Also, in a multi-core, multi-package system, it is always desirable to
> have all the timers firing on the cpus present in the same package.
> This would enable us to place the idle package in deep sleep
> state. So, migration of timers is required for this.
>
> A per_cpu sysfs hook is created
> at /sys/devices/system/cpu/cpuX/timer_migration. By echo-ing 1 to
> cpuX/timer_migration, all regular and hrtimers from cpuX are migrated
> to cpu0. The fact that all
> timers are migrated from cpuX to cpu0 is demonstrated by making a note
> of /proc/interrupts.
This seems like an exceedingly dumb idea - cpu 0 might be a long long
way from x and by pushing all timers to cpu0 you might actually overload
cpu 0.
Initially you talked about packages an moving timers to busy cpus -
which is something else altogether.
> $:echo 1 > /sys/devices/system/cpu/cpu3/timer_migration
> $:cat /proc/interrupts > file1; sleep 30 ; cat /proc/interrupts >
> file2
> $:diff file1 file2 | grep LOC
> < LOC: 5276 2100 2676 1647 2415
> 1803 2275 2977 Local timer interrupts
> > LOC: 6991 2195 2774 1647 2562
> 1900 2497 3075 Local timer interrupts
>
> As we can observe, first we are enabling timer migration in cpu3. As a
> result, the number of local timer interrupts on cpu3 over the next 30
> seconds are zero. cpu3 has been totally rid of all regular
> and hrtimers.
>
> Please refer to the following paper for details:
>
> http://ols.fedoraproject.org/OLS/Reprints-2008/srinivasan1-reprint.pdf
If there's anything worth reading in there it should have been mentioned
in this email and preferably in some comment in the code and Kconfig
help as well.
next prev parent reply other threads:[~2008-09-16 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 9:12 [RFC PATCH 0/1]: timers: Timer Migration Arun R Bharadwaj
2008-09-16 12:05 ` Peter Zijlstra [this message]
2008-09-16 16:47 ` Arun Bharadwaj
2008-09-17 7:35 ` Andrew Paprocki
2008-09-16 12:49 ` Andi Kleen
2008-09-16 13:53 ` Arjan van de Ven
2008-09-17 5:01 ` Arun R Bharadwaj
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=1221566730.6943.16.camel@lappy.programming.kicks-ass.net \
--to=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=arun@linux.vnet.ibm.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=vatsa@linux.vnet.ibm.com \
--cc=venkatesh.pallipadi@intel.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