Module unix

Expand description

This module defines the unix thread control.

The crate’s prelude doesn’t have much control over the unix threads, and this module provides better control over those.

Structs§

DeadlineFlags: Flags for controlling Deadline scheduling behavior.
SchedAttr: A copy of the Linux kernel’s sched_attr type.
ScheduleParams: Proxy structure to maintain compatibility between glibc and musl

NormalThreadSchedulePolicy: Normal (non-realtime) schedule policies For these schedule policies, niceness is used.
PriorityPolicyEdgeValueType: Defines the type of the priority edge value: minimum or maximum.
RealtimeThreadSchedulePolicy: The following “real-time” policies are also supported, for special time-critical applications that need precise control over the way in which runnable processes are selected for execution
ThreadSchedulePolicy: Thread schedule policy definition.

NICENESS_MAX: The maximum value possible for niceness. Threads with this value of niceness have the highest priority possible
NICENESS_MIN: The minimum value possible for niceness. Threads with this value of niceness have the lowest priority possible.

ThreadExt: A helper trait for other threads to implement to be able to call methods on threads themselves.

get_current_thread_priority: Get current thread’s priority value.
get_thread_priority: Get the thread’s priority value.
get_thread_scheduling_attributes: Returns scheduling attributes for the current thread.
set_current_thread_priority: Set current thread’s priority. In order to properly map a value of the thread priority, the thread scheduling must be known. This function attempts to retrieve the current thread’s scheduling policy and thus map the priority value correctly, so that it fits within the scheduling policy’s allowed range of values.
set_thread_priority_and_policy: Sets thread’s priority and schedule policy
thread_native_id: Returns current thread id, which is the current OS’s native handle. It may or may not be equal or even related to rust’s thread id, there is absolutely no guarantee for that.
thread_schedule_policy: Returns policy parameters (schedule policy and other schedule parameters) for current process
thread_schedule_policy_param: Returns policy parameters (schedule policy and other schedule parameters)