mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Ben Greear <greearb@candelatech.com>,
	Chris Friesen <cfriesen@nortelnetworks.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: sched_yield() version 2.4.24
Date: Wed, 31 Mar 2004 08:53:59 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0403310846290.10546@chaos> (raw)
In-Reply-To: <Pine.LNX.4.53.0403301526100.7833@chaos>

On Tue, 30 Mar 2004, Richard B. Johnson wrote:

> On Tue, 30 Mar 2004, Denis Vlasenko wrote:
>
> > On Tuesday 30 March 2004 19:52, Ben Greear wrote:
> > > Chris Friesen wrote:
> > > > The cpu util accounting code in kernel/timer.c hasn't changed in 2.4
> > > > since 2002.  Must be somewhere else.
> > > >
> > > > Anyone else have any ideas?
> > >
> > > As another sample point, I have fired up about 100 processes with
> > > each process having 10+ threads.  On my dual-xeon, I see maybe 15
> > > processes shown as 99% CPU in 'top'.  System load was near 25
> > > when I was looking, but the machine was still quite responsive.
> >
> > There was a top bug with exactly this symptom. Fixed.
> > I use procps-2.0.18.
> >
> Wonderful!  Now, where do I find the sources now that RedHat has
> gone "commercial" and is keeping everything secret?
>
> I followed the http://sources.redhat.com/procps/  instructions
> __exactly__ and get this:
>
> Script started on Tue Mar 30 15:27:02 2004
> quark:/home/johnson/foo[1] cvs -d :pserver:anoncvs@sources.redhat.com:/procps login anoncvs
> Logging in to :pserver:anoncvs@sources.redhat.com:2401/procps
> CVS password:
> /procps: no such repository
> quark:/home/johnson/foo[2] exit
> Script done on Tue Mar 30 15:28:32 2004
>

The RedHat server was apparently broken yesterday. There were many
persons who tried to get the source. Eventually Burton Windle
sent me a copy of the source, that he had previously acquired,
after he tried to access it also.

I compiled the source and the problem persists. Any task that
executes sched_yield() will get "charged" for the time that it
has given away. This is not correct. Maybe it is not correctable,
but it is still not correct. In addition to it being "unfair",
it messes up the totals because tasks that are using the CPU time
given up, also get charged.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  parent reply	other threads:[~2004-03-31 13:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-30 16:47 Richard B. Johnson
2004-03-30 16:58 ` Chris Friesen
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 [this message]
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=Pine.LNX.4.53.0403310846290.10546@chaos \
    --to=root@chaos.analogic.com \
    --cc=cfriesen@nortelnetworks.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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

all inboxes | Powered by JetHome®