From: "Chris Friesen" <cfriesen@nortel.com>
To: Xianghua Xiao <xiaoxianghua@gmail.com>
Cc: Con Kolivas <kernel@kolivas.org>,
Suresh Rajashekara <suresh.raj+linuxomap@gmail.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Issue with SCHED_FIFO app
Date: Mon, 17 May 2010 14:51:29 -0600 [thread overview]
Message-ID: <4BF1AC51.7080108@nortel.com> (raw)
In-Reply-To: <AANLkTilGJ8VVFM5sUEP3ZXOSaUSeGpxui7NkuUPRpM_m@mail.gmail.com>
On 05/12/2010 09:16 PM, Xianghua Xiao wrote:
> I'm unsure if the newest "top" (or /proc/PID/stat) reports the correct
> cpu usage when CFS/BFS is used, as you mentioned it seems failed to do
> that. I will try to stress the system and see who fails first under
> same workload, maybe that's the only way to compare cpu usage between
> 2.6.18rt vs 2.6.33rt, for now.
If you turn on scheduler debugging, then /proc/sched_debug gives
accurate information using the scheduler clock (at least with CFS, not
sure about BFS).
Chris
prev parent reply other threads:[~2010-05-17 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 4:39 Issue with SCHED_FIFO app Suresh Rajashekara
2010-05-10 4:42 ` Suresh Rajashekara
2010-05-12 2:46 ` Xianghua Xiao
2010-05-13 1:07 ` Robert Hancock
2010-05-13 2:49 ` Con Kolivas
2010-05-13 3:16 ` Xianghua Xiao
2010-05-17 20:51 ` Chris Friesen [this message]
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=4BF1AC51.7080108@nortel.com \
--to=cfriesen@nortel.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=suresh.raj+linuxomap@gmail.com \
--cc=xiaoxianghua@gmail.com \
/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.