From: Chris Friesen <cfriesen@nortelnetworks.com>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: sched_yield() version 2.4.24
Date: Tue, 30 Mar 2004 11:58:17 -0500 [thread overview]
Message-ID: <4069A729.3030507@nortelnetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0403301138260.6967@chaos>
Richard B. Johnson wrote:
> Anybody know why a task that does:
>
> for(;;)
> sched_yield();
>
> Shows 100% CPU utiliization when there are other tasks that
> are actually getting the CPU?
What do the other tasks show for cpu in top?
Maybe it's an artifact of the timer-based process sampling for cpu
utilization, and it just happens to be running when the timer interrupt
fires, so it keeps getting billed?
Chris
next prev parent reply other threads:[~2004-03-30 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 16:47 sched_yield() version 2.4.24 Richard B. Johnson
2004-03-30 16:58 ` Chris Friesen [this message]
2004-03-30 17:09 ` Richard B. Johnson
2004-03-30 17:30 ` Chris Friesen
2004-03-30 17:52 ` Ben Greear
2004-03-30 19:40 ` Denis Vlasenko
2004-03-30 20:29 ` Richard B. Johnson
2004-03-30 23:10 ` Diego Calleja García
2004-03-31 13:53 ` Richard B. Johnson
2004-04-01 0:05 ` Eric W. Biederman
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=4069A729.3030507@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox