Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

_lwp_getscheduler(2) [hpux man page]

_lwp_getscheduler(2)						System Calls Manual					      _lwp_getscheduler(2)

NAME
_lwp_getscheduler() - get LWP(Lightweight Process) scheduling policy and parameters SYNOPSIS
DESCRIPTION
The function allows the scheduling policy and parameters of an individual LWP within any process to be retrieved. The cmd argument determines the action to be performed by the system call. The following command is available. Other values of cmd are reserved for use by HP and may change without notice. The behavior of _lwp_getscheduler is undefined if any other value is passed to the cmd argument and it may change without notice. This request retrieves the scheduling policy and associated scheduling parameters for the LWP whose LWP ID is specified by target_lwp and store those in policy and param, respectively. If the value of target_lwp is zero(0), the target LWP will be the calling LWP. The priority value returned shall be the value specified by the most recent call affecting the target LWP(s) and will not reflect any tem- porary adjustments to its priority as a result of any priority inheritance or ceiling functions. Refer to the rtsched(2) manpage for a complete description of scheduling policies and priorities available. is similar to the function except that it operates on lightweight processes instead of processes. RETURN VALUE
Upon successful completion, returns with a value of 0; otherwise, it returns an error number to indicate the error. The variable is NOT set if an error occurs. ERRORS
For each of the following conditions, if the condition is detected, the function fails and returns the corresponding error number: The target process could not be accessed due to compartmental restrictions. The param parameter or the policy parameter points to an illegal address. The cmd parameter is invalid. No LWP can be found corresponding to that specified by target_lwp. WARNINGS
In general, the POSIX pthread interfaces should be used by multi-threaded applications. This system call may be used directly only when the application has a need to operate on LWPs in another process. This system call may result in undefined behavior if the usage is mixed with POSIX pthread APIs. SEE ALSO
_lwp_setscheduler(2), sched_getscheduler(2), pthread_getschedparam(3t). _lwp_getscheduler(2)

Check Out this Related Man Page

pthread_getschedparam(3T)												 pthread_getschedparam(3T)

NAME
pthread_getschedparam(), pthread_setschedparam() - get or set the scheduling policy and associated parameters SYNOPSIS
PARAMETERS
thread The thread whose scheduling policy and associated parameters are to be set/retrieved. policy This parameter either points to the memory location where the scheduling policy of thread is returned (get function) or it specifies the new value of the scheduling policy for thread (set function). param This parameter either points to the memory location where the scheduling parameters of thread are returned (get function) or it specifies the new scheduling parameters for thread (set function). DESCRIPTION
These functions allow the scheduling policy and associated parameters of threads within a multithreaded process to be retrieved and changed. The legal values for the scheduling policy and associated scheduling parameters are defined in changes the scheduling policy and associated scheduling parameters for thread to the policy and the associated parameters provided in pol- icy and param, respectively. On HP-UX, appropriate privileges are required to change the scheduling parameters of a thread. The calling process must have appropriate privileges or be a member of a group having access to successfully call The function retrieves the scheduling policy and associated parameters for thread and stores those values in policy and param, respec- tively. The values returned represent the actual scheduling values, not any temporary values that may be in effect due to priority inheri- tance or priority ceiling features. Notes For the and scheduling policies, only the sched_priority member of the structure is required in the associated scheduling parameters. All other scheduling policies have implementation-defined scheduling policies. Refer to the documentation for rtsched(2) and for further information on implementation-defined scheduling policies. RETURN VALUE
Upon successful completion, and return zero. Otherwise, an error number is returned to indicate the error (the variable is not set). ERRORS
If any of the following occur, the and functions return the corresponding error number: is not defined and these functions are not supported. For each of the following conditions, if the condition is detected, the function returns the corresponding error number: policy or one of the scheduling parameters in param is invalid. Either the policy or scheduling parameters contain an unsupported value. The caller does not have permission to set either the scheduling policy specified in policy or the scheduling parameters specified in param for thread. No thread could be found corresponding to thread. For each of the following conditions, if the condition is detected, the function returns the corresponding error number: No thread could be found corresponding to thread. The value specified by policy or param is invalid. AUTHOR
and were derived from the IEEE POSIX P1003.1c standard. SEE ALSO
pthread_attr_setschedparam(3T), pthread_attr_setschedpolicy(3T), pthread_attr_getschedparam(3T), pthread_attr_getschedpolicy(3T), rtsched(2). STANDARDS CONFORMANCE
Pthread Library pthread_getschedparam(3T)
Man Page