From: Ingo Molnar <mingo@elte.hu>
To: John Sigler <linux.kernel@free.fr>
Cc: linux-rt-users@vger.kernel.org,
oprofile-list@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Pin-pointing the root of unusual application latencies
Date: Wed, 25 Jul 2007 15:05:36 +0200 [thread overview]
Message-ID: <20070725130536.GA12334@elte.hu> (raw)
In-Reply-To: <46A74A58.1070704@free.fr>
* John Sigler <linux.kernel@free.fr> wrote:
> >With a pair of the following in the middle:
> >
> >softirq--4 0.... 670us : call_rcu (rt_run_flush)
> >softirq--4 0D..1 670us : __rcu_advance_callbacks (call_rcu)
> Any idea what went wrong in the above function trace? Why is the
> kernel spinning in circles that way?
does your test-app have higher priority than softirq--4 ?
Ingo
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: John Sigler <linux.kernel@free.fr>
Cc: linux-rt-users@vger.kernel.org,
oprofile-list@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Pin-pointing the root of unusual application latencies
Date: Wed, 25 Jul 2007 15:05:36 +0200 [thread overview]
Message-ID: <20070725130536.GA12334@elte.hu> (raw)
In-Reply-To: <46A74A58.1070704@free.fr>
* John Sigler <linux.kernel@free.fr> wrote:
> >With a pair of the following in the middle:
> >
> >softirq--4 0.... 670us : call_rcu (rt_run_flush)
> >softirq--4 0D..1 670us : __rcu_advance_callbacks (call_rcu)
> Any idea what went wrong in the above function trace? Why is the
> kernel spinning in circles that way?
does your test-app have higher priority than softirq--4 ?
Ingo
next prev parent reply other threads:[~2007-07-25 13:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 10:22 Pin-pointing the root of unusual application latencies John Sigler
2007-07-13 8:32 ` John Sigler
2007-07-23 8:25 ` John Sigler
2007-07-23 9:53 ` Ingo Molnar
2007-07-23 14:14 ` John Sigler
2007-07-23 16:04 ` Ingo Molnar
2007-07-23 16:04 ` Ingo Molnar
2007-07-23 16:44 ` John Sigler
2007-07-24 8:31 ` John Sigler
2007-07-24 9:20 ` John Sigler
2007-07-25 13:04 ` John Sigler
2007-07-25 13:05 ` Ingo Molnar [this message]
2007-07-25 13:05 ` Ingo Molnar
2007-07-25 13:20 ` John Sigler
2007-07-25 13:38 ` Ingo Molnar
2007-07-25 14:05 ` John Sigler
2007-07-25 14:13 ` Alessio Igor Bogani
2007-07-25 14:35 ` John Sigler
2007-07-25 15:00 ` Alessio Igor Bogani
2007-07-25 15:21 ` John Sigler
2007-07-25 15:35 ` Alessio Igor Bogani
2007-07-25 15:53 ` John Sigler
2007-07-25 15:28 ` Karsten Wiese
2007-07-25 15:46 ` John Sigler
2007-07-25 16:31 ` Karsten Wiese
2007-07-25 17:09 ` Len Brown
2007-07-26 8:35 ` John Sigler
2007-07-26 10:45 ` John Sigler
2007-07-26 12:02 ` John Sigler
2007-07-26 15:16 ` John Sigler
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=20070725130536.GA12334@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux.kernel@free.fr \
--cc=oprofile-list@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.