public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: delayacct regression in 2.6.24 git
Date: Fri, 02 Nov 2007 21:58:14 +0530	[thread overview]
Message-ID: <472B501E.9000307@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071102152529.GB20134@elte.hu>

Ingo Molnar wrote:
> * Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> 
>> Hi, Ingo,
>>
>> I missed commit 75d4ef16a6aa84f708188bada182315f80aab6fa
>> "sched: fix delay accounting performance regression"
>>
>> Without these changes, I find that delay accounting does
>> not work as expected, I see zeros in the field for virtual,delay
>> and count(s).
>>
>> CPU             count     real total  virtual total    delay total
>>                     0      535861848              0              0
>>
>>
>> This breaks existing delay accounting behaviour.
>>
>> Am I missing something?
> 
> delay accounting was causing context-switch slowdown because it called 
> sched_clock() explicitly - but indeed my fix to that is wrong ...
> 
> how about reverting the change but also using rq->clock instead of 
> sched_clock()?

Hmm... I think that might work, I find that schedule() calls
__update_rq_clock() which in turn calls sched_clock(), so it
might be a worthwhile optimization.

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

  reply	other threads:[~2007-11-02 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 13:41 delayacct regression in 2.6.24 git Balbir Singh
2007-11-02 15:25 ` Ingo Molnar
2007-11-02 16:28   ` Balbir Singh [this message]
2007-11-03  8:31     ` Ingo Molnar

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=472B501E.9000307@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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