public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>, tglx@linutronix.de
Subject: Re: nohz and strange sleep latencies
Date: Tue, 20 Nov 2007 10:05:55 +0100	[thread overview]
Message-ID: <20071120090555.GA21424@elte.hu> (raw)
In-Reply-To: <20071120085704.GA19950@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> > hpet-disable helps.. a bit. 200msec latencies are gone. (What is 
> > used for wakeups in this case?)
> > 
> > pavel@amd:~$ while true; do time sleep 0.01; done
> > 0.00user 0.00system 0.01 (0m0.013s) elapsed 22.96%CPU
> > 0.00user 0.00system 0.01 (0m0.018s) elapsed 11.05%CPU
> > 0.00user 0.00system 0.01 (0m0.013s) elapsed 15.54%CPU
> 
> could you run this while doing the sleep test:
> 
>   http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info.sh
> 
> and send us the output? (Enabling CONFIG_TIMER_STATS, 
> CONFIG_SCHED_DEBUG and CONFIG_SCHEDSTATS would maximize the amount of 
> information.)

another question: do you feel and see these timer latencies? If unsure 
you can do a timing test from a remote (known-good) box:

   while :; do time ssh testbox sleep 0.01; done

there'll be a fair bit of offset cost and noise, but these fluctuations 
should still be there and should be noticeable.

but i suspect the delays are "real", i.e. caused by timers not firing at 
the right moment and not by some GTOD anomaly. Once you send the debug 
data we might be able to tell more.

	Ingo

  reply	other threads:[~2007-11-20  9:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 20:31 nohz and strange sleep latencies Pavel Machek
2007-11-19 20:55 ` Ingo Molnar
2007-11-19 21:11   ` Pavel Machek
2007-11-20  8:57     ` Ingo Molnar
2007-11-20  9:05       ` Ingo Molnar [this message]
2007-11-20 10:54       ` Pavel Machek
2007-11-20 20:54         ` Ingo Molnar
2007-11-20 22:48           ` Thomas Gleixner
2007-11-20 22:52             ` Ingo Molnar
2007-11-22 10:09               ` Pavel Machek
2007-11-22 18:51               ` Pavel Machek
2007-11-22 18:52               ` Pavel Machek
2007-11-22 20:29                 ` Thomas Gleixner
2007-11-23 12:22                   ` Pavel Machek
2007-11-24 22:29                   ` Pavel Machek
2007-11-24 22:40                   ` Pavel Machek
2007-11-24 23:29                     ` Rafael J. Wysocki
2007-11-24 23:35                       ` Rafael J. Wysocki
2007-11-25 21:51                       ` Thomas Gleixner
2007-11-25 20:25                   ` [patch] " Pavel Machek
2007-11-25 21:42                     ` Thomas Gleixner
2007-11-26 11:54                   ` Pavel Machek
2007-11-20  9:44 ` Thomas Gleixner

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=20071120090555.GA21424@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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