MirOS Manual: pthread_getschedparam(3), pthread_schedparam(3), pthread_setschedparam(3)

PTHREAD_SCHEDPARAM(3)      BSD Programmer's Manual       PTHREAD_SCHEDPARAM(3)

NAME

     pthread_setschedparam, pthread_getschedparam - thread scheduling parame-
     ter manipulation

SYNOPSIS

     #include <pthread.h>

     int
     pthread_setschedparam(pthread_t thread, int policy,
             const struct sched_param *param);

     int
     pthread_getschedparam(pthread_t thread, int *policy,
             struct sched_param *param);

DESCRIPTION

     The pthread_setschedparam() and pthread_getschedparam() functions set and
     get the scheduling parameters of individual threads. The scheduling poli-
     cy for a thread can either be SCHED_FIFO (first in, first out) or
     SCHED_RR (round-robin). The thread priority (accessed via param-
     >sched_priority) must be at least PTHREAD_MIN_PRIORITY and no more than
     PTHREAD_MAX_PRIORITY.

RETURN VALUES

     If successful, these functions return 0. Otherwise, an error number is
     returned to indicate the error.

ERRORS

     pthread_setschedparam() will fail if:

     [EINVAL]      Invalid value for policy.

     [ENOTSUP]     Invalid value for scheduling parameters.

     [ESRCH]       Non-existent thread thread.

     pthread_getschedparam() will fail if:

     [ESRCH]       Non-existent thread thread.

STANDARDS

     pthread_setschedparam() and pthread_getschedparam() conform to Version 2
     of the Single UNIX Specification

MirOS BSD #10-current            May 1, 2000                                 1

Generated on 2014-07-04 21:17:45 by $MirOS: src/scripts/roff2htm,v 1.79 2014/02/10 00:36:11 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002‒2014 The MirOS Project, Germany.
This product includes material provided by Thorsten Glaser.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.