From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Giovanni Tusa <gtusa@inwind.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sched_yield behavior
Date: Mon, 28 Feb 2005 09:04:57 +1100 [thread overview]
Message-ID: <42224409.8010809@yahoo.com.au> (raw)
In-Reply-To: <00e901c51cbb$45b3cac0$65071897@gtusa>
Giovanni Tusa wrote:
> If I am not wrong, the scheduler will choose it again (it will be still the
> higher priority task, and the only of its priority list).
> I have to add an explicit sleep to effectively relinquish the CPU for some
> time, or the scheduler can deal with such a
> situation in another way?
Yes, the scheduler will choose it again. This behaviour is also
specified in the relevant standards.
Your alternatives may be to use other methods of userspace
synchronisation (eg. pipes, semaphores), or to use timers.
next prev parent reply other threads:[~2005-02-27 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 10:58 sched_yield behavior Giovanni Tusa
2005-02-27 17:02 ` Lee Revell
2005-02-27 22:04 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-01 11:15 gtusa
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=42224409.8010809@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=gtusa@inwind.it \
--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