LKML Archive on
help / color / mirror / Atom feed
From: Ingo Molnar <>
To: "Carlos R. Mafra" <>
Subject: Re: Interactivity issue in 2.6.25-rc3
Date: Fri, 29 Feb 2008 17:04:08 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


* Carlos R. Mafra <> wrote:

> Is it an scheduler anomaly if 'se.wait_max' is bigger than 40 msecs 
> for _any_ of the processes which appear in the debug script log? In 
> other words, is the scheduler mathematically build to not allow 
> latencies higher than 40 msecs?

it is definitely an anomaly if it's bigger than 40 msecs if you clear 
all stats via and the large latencies appear 
after that. You can force it to go above 40 msecs if you run more than 
say 40 CPU hogs in parallel, so it's not "mathematical", but you should 
never see large latencies under normal workloads - and that includes 
almost everything but "insanely high" workloads.

and obviously, even if you only 'feel' long delays that's too an anomaly 
by definition, no matter what the scripts say about it. It might even be 
a scheduler anomaly as well: for example if the scheduler clock has an 
anomaly - on which the delay statistics are based too.

generally, latencytop gives a pretty good idea about where app delays 
come from. (As a second-level mechanism, in sched-devel.git you can try 
the latency tracer.)


  parent reply	other threads:[~2008-02-29 16:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 18:44 Carlos R. Mafra
2008-02-28 19:18 ` Ingo Molnar
2008-02-28 19:54   ` Ray Lee
     [not found]     ` <>
2008-02-28 21:28       ` Ray Lee
2008-02-29 15:57         ` Ingo Molnar
2008-02-29 18:33           ` Ray Lee
2008-02-29 16:04       ` Ingo Molnar [this message]
2008-02-29 17:14         ` Carlos R. Mafra
2008-02-29 18:36           ` Ingo Molnar
2008-02-28 21:21 Carlos R. Mafra

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: Interactivity issue in 2.6.25-rc3' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).