[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070521081201.GB13858@elte.hu>
Date: Mon, 21 May 2007 10:12:01 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Anant Nitya <kernel@...chanda.info>
Cc: linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: bad networking related lag in v2.6.22-rc2
* Ingo Molnar <mingo@...e.hu> wrote:
> > ouch! a nearly 1 second delay got observed by the scheduler - something
> > is really killing your system!
>
> ah, you got the latency tracer from Thomas, as part of the -hrt patchset
> - that makes it quite a bit easier to debug. [...]
and ... you already did a trace for Thomas, for the softirq problem:
http://cybertek.info/taitai/trace.txt.bz2
this trace shows really bad networking related kernel activities!
gkrellm-5977 does this at timestamp 0:
gkrellm-5977 0..s. 0us : cond_resched_softirq (established_get_next)
2 milliseconds later it's still in established_get_next() (!):
gkrellm-5977 0..s. 2001us : cond_resched_softirq (established_get_next)
and the whole thing takes ... 455 msecs:
gkrellm-5977 0..s. 455443us+: cond_resched_softirq (established_get_next)
i think this suggests that you have tons of open sockets. What does
"netstat -ts" say on your box?
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists