From: Nick Piggin <piggin@cyberone.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Process scheduler fairness bug (feature?)
Date: Mon, 07 Jul 2003 21:32:53 +1000 [thread overview]
Message-ID: <3F095A65.4070100@cyberone.com.au> (raw)
Hi Con,
In recent testing unrelated to your interactivity stuff,
I have found the following with 74-mm2, although I don't
think its due to your interactivity stuff.
I don't have a real workload that is bothered by this btw.
Just wondering if its fixable, or there is a reason for it.
On UP, 2 processes of same priority. One is doing an
infinite loop of nothing, the other doing an infinite loop
of fork+waiting for children which count to a million then
exit (do a bit of work).
The non forking CPU hog gets 75% of the cpu.
reply other threads:[~2003-07-07 11:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F095A65.4070100@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
/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.