From: Arjan van de Ven <arjan@infradead.org>
To: svaidy@linux.vnet.ibm.com
Cc: discuss@LessWatts.org,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Dipankar Sarma <dipankar@in.ibm.com>, Ingo Molnar <mingo@elte.hu>,
venkatesh.pallipadi@intel.com, tglx@linutronix.de,
suresh.b.siddha@intel.com, Gautham R Shenoy <ego@in.ibm.com>,
Chanda Sethia <chanda.sethia@in.ibm.com>
Subject: Re: Too many timer interrupts in NO_HZ
Date: Sun, 2 Mar 2008 11:57:09 -0800 [thread overview]
Message-ID: <20080302115709.30403490@laptopd505.fenrus.org> (raw)
In-Reply-To: <20080302194812.GD10028@dirshya.in.ibm.com>
On Mon, 3 Mar 2008 01:18:13 +0530
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com> wrote:
> Hi,
>
> I am trying to play around with the tickless kernel and
> sched_mc_power_savings tunables to increase the idle duration of the
> CPU in an SMP server. sched_mc_power_savings provides good
> consolidation of long running jobs when the system is lightly loaded.
> However I am interested to see CPU idle times for couple minutes on
> atleast few CPUs in an completely idle SMP system.
>
> I have posted related instrumentation results at
> http://lkml.org/lkml/2008/1/8/243
>
> The experimental setup is identical. Just that I have tried to
> collect more data and also bias the wakeup logic.
>
> The kernel is 2.6.25-rc3 with NO_HZ, SCHED_MC, HIGH_RES_TIMERS, and
> HPET turned on.
>
> I have tried to collect interesting data from tick-sched.c, sched.c
> and softirq.c.
>
> As suggested by Ingo in the previous thread, I have hacked the sched.c
> try_to_wake_up logic so that I can force all wake-ups to happen on
> CPU0. This is just and experiment, in reality we will have to
> carefully choose a domain and CPU to bias all wakeups on an idle
> system.
please show us powertop -d output; that way we can at least see sort of what
is going on...
next prev parent reply other threads:[~2008-03-02 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 19:48 Vaidyanathan Srinivasan
2008-03-02 19:57 ` Arjan van de Ven [this message]
2008-03-02 20:25 ` Vaidyanathan Srinivasan
2008-03-05 15:38 ` Vaidyanathan Srinivasan
2008-03-16 18:17 ` Vaidyanathan Srinivasan
2008-03-17 2:34 ` [linux-pm] " Alan Stern
2008-03-17 8:44 ` David Brownell
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=20080302115709.30403490@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=chanda.sethia@in.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=discuss@LessWatts.org \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®