Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sched_yield(3c) [opensolaris man page]

sched_yield(3C) 					   Standard C Library Functions 					   sched_yield(3C)

NAME
sched_yield - yield processor SYNOPSIS
#include <sched.h> int sched_yield(void); DESCRIPTION
The sched_yield() function forces the running thread to relinquish the processor until the process again becomes the head of its process list. It takes no arguments. RETURN VALUES
If successful, sched_yield() returns 0, otherwise, it returns -1, and sets errno to indicate the error condition. ERRORS
No errors are defined. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ |ATTRIBUTE TYPE |ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ SEE ALSO
librt(3LIB), sched.h(3HEAD), attributes(5), standards(5) SunOS 5.11 5 Feb 2008 sched_yield(3C)

Check Out this Related Man Page

SCHED_YIELD(2)						     Linux Programmer's Manual						    SCHED_YIELD(2)

NAME
sched_yield - yield the processor SYNOPSIS
#include <sched.h> int sched_yield(void); DESCRIPTION
sched_yield() causes the calling thread to relinquish the CPU. The thread is moved to the end of the queue for its static priority and a new thread gets to run. RETURN VALUE
On success, sched_yield() returns 0. On error, -1 is returned, and errno is set appropriately. ERRORS
In the Linux implementation, sched_yield() always succeeds. CONFORMING TO
POSIX.1-2001. NOTES
If the calling thread is the only thread in the highest priority list at that time, it will continue to run after a call to sched_yield(). POSIX systems on which sched_yield() is available define _POSIX_PRIORITY_SCHEDULING in <unistd.h>. Strategic calls to sched_yield() can improve performance by giving other threads or processes a chance to run when (heavily) contended resources (e.g., mutexes) have been released by the caller. Avoid calling sched_yield() unnecessarily or inappropriately (e.g., when resources needed by other schedulable threads are still held by the caller), since doing so will result in unnecessary context switches, which will degrade system performance. SEE ALSO
sched_setscheduler(2) for a description of Linux scheduling Programming for the real world - POSIX.4 by Bill O. Gallmeister, O'Reilly & Associates, Inc., ISBN 1-56592-074-0. COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2008-10-18 SCHED_YIELD(2)
Man Page

Featured Tech Videos