From: Ingo Molnar <mingo@elte.hu>
To: Anant Nitya <kernel@prachanda.info>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: bad networking related lag in v2.6.22-rc2
Date: Mon, 21 May 2007 10:03:51 +0200 [thread overview]
Message-ID: <20070521080351.GA13375@elte.hu> (raw)
In-Reply-To: <20070521075824.GA11198@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> ok, i got your -rc2 debug numbers (off-list), and it doesnt look pretty:
>
> before-lag:
>
> sleep_max : 259502076
> block_max : 27690921
> wait_max : 16381558
>
> after-lag:
>
> sleep_max : 584186160
> block_max : 261780071
> wait_max : 881255577
>
> ouch! a nearly 1 second delay got observed by the scheduler - something
> is really killing your system!
>
> what does 'top' show during an upload? Is any system related task out
> of whack? Could you try to get a readprofile or an oprofile output
> from the kernel, so that we can see what is slowing it down so much?
> It could be something networking related in v2.6.22-rc2.
ah, you got the latency tracer from Thomas, as part of the -hrt patchset
- that makes it quite a bit easier to debug. Could you run the attached
trace-it-10sec utility:
trace-it-10sec > trace-to-ingo.txt
and send me the (compressed) trace output (off-list, or post an URL to
the trace)? Try to reproduce the 'lag' event in the 10 seconds while the
tracer is running.
Ingo
next prev parent reply other threads:[~2007-05-21 8:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 17:45 [patch] CFS scheduler, -v13 Ingo Molnar
2007-05-17 21:47 ` Anant Nitya
2007-05-18 10:26 ` Ingo Molnar
2007-05-18 16:13 ` Anant Nitya
2007-05-19 21:16 ` Anant Nitya
2007-05-20 6:38 ` Ingo Molnar
2007-05-21 7:58 ` bad networking related lag in v2.6.22-rc2 Ingo Molnar
2007-05-21 8:03 ` Ingo Molnar [this message]
2007-05-21 8:05 ` Ingo Molnar
2007-05-21 8:12 ` Ingo Molnar
2007-05-21 8:29 ` David Miller
2007-05-21 10:09 ` Ingo Molnar
2007-05-21 10:14 ` Anant Nitya
2007-05-21 10:20 ` Ingo Molnar
2007-05-22 6:20 ` Anant Nitya
2007-05-21 19:40 ` Anant Nitya
2007-05-21 20:46 ` Ingo Molnar
2007-05-21 21:02 ` Patrick McHardy
2007-05-21 21:30 ` Patrick McHardy
2007-05-22 6:17 ` Anant Nitya
2007-05-22 6:22 ` Ingo Molnar
2007-05-23 5:40 ` Anant Nitya
2007-05-23 6:30 ` Ingo Molnar
2007-05-23 10:56 ` Patrick McHardy
2007-05-23 11:05 ` Ingo Molnar
2007-05-23 11:25 ` Herbert Xu
2007-05-23 11:33 ` Patrick McHardy
2007-05-23 15:00 ` Linus Torvalds
2007-05-23 17:16 ` Patrick McHardy
2007-05-23 11:40 ` Ingo Molnar
2007-05-23 21:30 ` David Miller
2007-05-24 5:41 ` Patrick McHardy
2007-05-24 6:40 ` David Miller
2007-05-24 7:12 ` Anant Nitya
2007-05-22 6:23 ` Ingo Molnar
2007-05-22 6:24 ` Ingo Molnar
2007-05-22 9:17 ` Patrick McHardy
2007-05-22 12:47 ` Anant Nitya
2007-05-21 8:25 ` David Miller
2007-05-21 8:28 ` Ingo Molnar
2007-05-21 8:30 ` David Miller
2007-05-21 15:57 ` [patch] CFS scheduler, -v13 Linus Torvalds
2007-05-22 22:06 ` Bill Davidsen
2007-05-23 5:45 ` Anant Nitya
2007-05-18 15:20 ` Michael Lothian
2007-05-18 15:56 ` 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=20070521080351.GA13375@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kernel@prachanda.info \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome