From: Arun R Bharadwaj <arun@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linux-pm@lists.linux-foundation.org
Cc: a.p.zijlstra@chello.nl, ego@in.ibm.com, tglx@linutronix.de,
mingo@elte.hu, andi@firstfloor.org,
venkatesh.pallipadi@intel.com, vatsa@linux.vnet.ibm.com,
arjan@infradead.org, svaidy@linux.vnet.ibm.com,
arun@linux.vnet.ibm.com, Richard Henderson <rth@twiddle.net>,
Chris Zankel <chris@zankel.net>,
Mikael Starvik <starvik@axis.com>,
Jesper Nilsson <jesper.nilsson@axis.com>,
Tony Luck <tony.luck@intel.com>, Kyle McMartin <kyle@mcmartin.ca>
Subject: [v6 PATCH 0/4] timers: Framework for migration of timers
Date: Thu, 16 Apr 2009 12:11:36 +0530 [thread overview]
Message-ID: <20090416064136.GA7510@linux.vnet.ibm.com> (raw)
Ingo, Thomas, all,
In an SMP system, tasks are scheduled on different CPUs by the
scheduler, interrupts are managed by irqbalancer daemon, but timers
are still stuck to the CPUs that they have been initialised. Timers
queued by tasks gets re-queued on the CPU where the task gets to run
next, but timers from IRQ context like the ones in device drivers are
still stuck on the CPU they were initialised. This framework will
help move all 'movable timers' using a sysctl interface.
Please consider for inclusion into -tip
Testing Carried Out:
* Kernbench on a 2-package, quad-core machine results are as follows:
-----------------------------------------------------------------------
| No. of Threads | Time(s) - Without | Time(s) - With the |
| | patches applied | patches applied |
-----------------------------------------------------------------------
| 2 | 106.9 | 106.3 |
| 4 | 54.7 | 54.4 |
| 8 | 31.5 | 31.1 |
| 16 | 28.0 | 27.5 |
| 32 | 28.1 | 28.9 |
-----------------------------------------------------------------------
* I have cross-compiled my patches against alpha architecture in order
to test if my patches have any issues for architectures without
clockevents support.
The patches cross-compile without any issues for alpha architecture,
but I need help to test if there is any performance regression.
So I'm Cc-ing the maintainers of architectures without clockevents support.
The following patches are included:
PATCH 1/4 - framework to identify pinned timers.
PATCH 2/4 - identifying the existing pinned hrtimers.
PATCH 3/4 - /proc/sys sysctl hook to enable timer migration.
PATCH 4/4 - logic to enable timer migration.
The patchset is based on the latest tip/master.
Timer migration is enabled by default.
It can be turned off when CONFIG_SCHED_DEBUG=y by
echo 0 > /proc/sys/kernel/timer_migration
--arun
next reply other threads:[~2009-04-16 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 6:41 Arun R Bharadwaj [this message]
2009-04-16 6:43 ` [v6 PATCH 1/4] timers: Framework for identifying pinned timers Arun R Bharadwaj
2009-04-16 6:44 ` [v6 PATCH 2/4] timers: Identifying the existing " Arun R Bharadwaj
2009-04-16 6:45 ` [v6 PATCH 3/4] timers: /proc/sys sysctl hook to enable timer migration Arun R Bharadwaj
2009-04-16 6:46 ` [v6 PATCH 4/4] timers: Logic to move non pinned timers 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=20090416064136.GA7510@linux.vnet.ibm.com \
--to=arun@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=chris@zankel.net \
--cc=ego@in.ibm.com \
--cc=jesper.nilsson@axis.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=rth@twiddle.net \
--cc=starvik@axis.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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