From: Duraid Madina <duraid@octopus.com.au>
To: arjanv@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Linux-ia64] Re: web page on O(1) scheduler
Date: Thu, 22 May 2003 05:18:02 +1000 [thread overview]
Message-ID: <3ECBD0EA.70307@octopus.com.au> (raw)
In-Reply-To: <1053522732.1301.4.camel@laptop.fenrus.com>
Arjan van de Ven wrote:
> if you had spent the time you spent on this colorful graphic on reading
> SUS or Posix about what sched_yield() means
Quoth the man page,
"A process can relinquish the processor voluntarily without blocking by
calling sched_yield. The process will then be moved to the end of the
queue for its static priority and a new process gets to run."
How you get from there to "I'm the least important thing in the system"
is, once again, beyond me. And even if that were a reasonable
interpretation of the word 'yield', you would still hope that more than
one CPU would get something to do if there was enough work to go around.
Agreed, "spinning" on sched_yield is a very naive way of doing
spinlocks. But that doesn't change the fact that it's a simple and
correct way. One would have hoped that calling sched_yield every few
million cycles wouldn't break the scheduler.
Duraid
next prev parent reply other threads:[~2003-05-21 19:05 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 6:49 web page on O(1) scheduler David Mosberger
2003-05-21 9:01 ` Arjan van de Ven
2003-05-21 10:40 ` [Linux-ia64] " Duraid Madina
2003-05-21 10:43 ` Christoph Hellwig
2003-05-21 13:12 ` Arjan van de Ven
2003-05-21 13:51 ` Olivier Galibert
2003-05-28 22:12 ` Bill Davidsen
[not found] ` <Pine.LNX.3.96.1030528180909.21414B-100000@gatekeeper.tmr.c om>
2003-05-29 5:59 ` Mike Galbraith
2003-06-02 8:05 ` Ingo Molnar
2003-06-04 4:07 ` Bill Davidsen
[not found] ` <Pine.LNX.4.44.0306020949520.3375-100000@localhost.localdom ain>
2003-06-02 13:51 ` Mike Galbraith
2003-06-04 3:52 ` Bill Davidsen
2003-06-04 4:55 ` David Schwartz
[not found] ` <Pine.LNX.3.96.1030603234616.16495B-100000@gatekeeper.tmr.c om>
2003-06-04 7:13 ` Mike Galbraith
2003-06-04 15:30 ` Jan Harkes
2003-05-21 19:18 ` Duraid Madina [this message]
2003-05-21 20:03 ` Helge Hafting
2003-05-21 22:59 ` Alan Cox
2003-05-21 15:18 ` David Mosberger
2003-05-23 1:07 ` [Linux-ia64] " Hans Boehm
2003-05-23 8:30 ` Arjan van de Ven
2003-05-21 9:26 ` Mike Galbraith
2003-05-21 9:30 ` Mike Galbraith
2003-05-21 17:56 ` David Mosberger
2003-05-21 20:46 ` Mike Galbraith
2003-05-22 9:52 ` Mike Galbraith
2003-05-22 16:25 ` Mike Galbraith
2003-05-22 17:58 ` David Mosberger
2003-05-27 15:16 ` [case closed] " Mike Galbraith
2003-06-03 20:59 ` sched.c gives ICE [Was: Re: web page on O(1) scheduler] J.A. Magallon
2003-06-03 22:29 ` Mike Galbraith
2003-06-22 22:03 ` J.A. Magallon
2003-06-22 22:10 ` J.A. Magallon
2003-05-22 0:38 ` web page on O(1) scheduler Rik van Riel
[not found] ` <Pine.LNX.4.50L.0305212038120.5425-100000@imladris.surriel. com>
2003-05-22 5:52 ` Mike Galbraith
2003-05-22 14:47 ` Valdis.Kletnieks
2003-05-22 16:12 ` Mike Galbraith
2003-05-25 9:17 ` Mike Galbraith
2003-05-21 18:31 ` [Linux-ia64] " David Mosberger
2003-05-21 20:00 ` Cyclades Cyclom-Y ISA on 2.5.69 John Stoffel
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 17:48 [Linux-ia64] Re: web page on O(1) scheduler Boehm, Hans
2003-05-23 18:04 ` Davide Libenzi
2003-05-24 0:10 Boehm, Hans
2003-05-24 0:20 ` Davide Libenzi
2003-05-24 0:53 Boehm, Hans
2003-05-24 5:38 ` Davide Libenzi
2003-05-24 14:43 ` Davide Libenzi
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=3ECBD0EA.70307@octopus.com.au \
--to=duraid@octopus.com.au \
--cc=arjanv@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox