From: Ingo Molnar <mingo@elte.hu>
To: Venki Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Track accurate idle time with tick_sched.idle_sleeptime
Date: Fri, 31 Aug 2007 20:22:12 +0200 [thread overview]
Message-ID: <20070831182212.GA3568@elte.hu> (raw)
In-Reply-To: <20070827215611.GA30396@linux-os.sc.intel.com>
* Venki Pallipadi <venkatesh.pallipadi@intel.com> wrote:
> Current idle time in kstat is based on jiffies and is coarse grained.
> tick_sched.idle_sleeptime is making some attempt to keep track of idle
> time in a fine grained manner. But, it is not handling the time spent
> in interrupts fully.
>
> Make tick_sched.idle_sleeptime accurate with respect to time spent on
> handling interrupts and also add tick_sched.idle_lastupdate, which
> keeps track of last time when idle_sleeptime was updated.
>
> This statistics will be crucial for cpufreq-ondemand governor, which
> can shed some conservative gaurd band that is uses today while setting
> the frequency. The ondemand changes that uses the exact idle time is
> coming soon.
nice stuff! I've added your patch to the scheduler queue - but this will
probably be 2.6.24 material.
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
next prev parent reply other threads:[~2007-08-31 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 21:56 [PATCH] Track accurate idle time with tick_sched.idle_sleeptime Venki Pallipadi
2007-08-31 18:22 ` Ingo Molnar [this message]
2007-08-31 18:24 ` Ingo Molnar
2007-08-31 18:26 ` Pallipadi, Venkatesh
2007-09-01 22:23 ` Andi Kleen
2007-09-02 7:28 ` Ingo Molnar
2007-09-02 7:46 ` Andi Kleen
2007-09-02 10:02 ` Ingo Molnar
2007-09-10 18:59 ` Pallipadi, Venkatesh
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=20070831182212.GA3568@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.