From: Davide Libenzi <davidel@xmailserver.org>
To: Fabrice Peix <Fabrice.Peix@sophia.inria.fr>
Cc: KML <linux-kernel@vger.kernel.org>
Subject: RE: sched_yield
Date: Sun, 25 Feb 2001 10:52:08 -0800 (PST) [thread overview]
Message-ID: <XFMail.20010225105208.davidel@xmailserver.org> (raw)
In-Reply-To: <3A994FBC.691A143C@sophia.inria.fr>
On 25-Feb-2001 Fabrice Peix wrote:
>
>
>
> Yop,
>
> Just a newbie question ...
> Why sys_sched_yield don't call schedule ?
>
>
> man page of sched_yield tell :
>
> "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."
>
It sets, under certain conditions ( nr_running ), the variable need_resched
and, in the system call return code this value is checked and schedule() is
called.
Look at sched.c and entry.S.
- Davide
prev parent reply other threads:[~2001-02-25 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 18:32 sched_yield Fabrice Peix
2001-02-25 18:52 ` Davide Libenzi [this message]
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=XFMail.20010225105208.davidel@xmailserver.org \
--to=davidel@xmailserver.org \
--cc=Fabrice.Peix@sophia.inria.fr \
--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