sched.h(0P)

🌸 sched.h (0P) β€” POSIX Programmer's Manual 🌸

okay bestie, we're doing the POSIX Programmer's Manual version of this page, and it's giving very much "read the fine print" energy, so let's go πŸ’…

πŸ’¬ PROLOG

This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ β€” so like, consult the corresponding Linux manual page for the deets on Linux behavior β€” or honestly, the interface may not even be implemented on Linux at all. πŸ™ˆ

no cap, always check your platform. POSIX says one thing, your kernel might say another.

✨ NAME ✨

sched.h β€” execution scheduling πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

#include <sched.h>

πŸ’– DESCRIPTION πŸ’–

The <sched.h> header shall define the pid_t type as described in <sys/types.h>.

The <sched.h> header shall define the time_t type as described in <sys/types.h>.

The <sched.h> header shall define the timespec structure as described in <time.h>.

The <sched.h> header shall define the sched_param structure, which shall include the scheduling parameters required for implementation of each supported scheduling policy. This structure shall include at least the following member:

int       sched_priority        Process or thread execution scheduling priority.

The sched_param structure defined in <sched.h> shall include the following members in addition to those specified above:

int             sched_ss_low_priority Low scheduling priority for
                                       sporadic server.
struct timespec sched_ss_repl_period  Replenishment period for
                                       sporadic server.
struct timespec sched_ss_init_budget  Initial budget for sporadic server.
int             sched_ss_max_repl     Maximum pending replenishments for
                                       sporadic server.

so basically: every process or thread is controlled by an associated scheduling policy and priority. 🧚 Associated with each policy is a priority range. Each policy definition specifies the minimum priority range for that policy. And plot twist β€” the priority ranges for each policy may overlap the priority ranges of other policies. it's giving overlapping venn diagram realness. 🌈

Four scheduling policies are defined; others may be defined by the implementation. The four standard policies are indicated by the values of the following symbolic constants:

  • SCHED_FIFO β€” First in-first out (FIFO) scheduling policy.
  • SCHED_RR β€” Round robin scheduling policy.
  • SCHED_SPORADIC β€” Sporadic server scheduling policy.
  • SCHED_OTHER β€” Another scheduling policy.

The values of these constants are distinct. (yes bestie, no two of them are the same, we checked 😌)

The following shall be declared as functions and may also be defined as macros. Function prototypes shall be provided.

int    sched_get_priority_max(int);
int    sched_get_priority_min(int);
int    sched_getparam(pid_t, struct sched_param *);
int    sched_getscheduler(pid_t);
int    sched_rr_get_interval(pid_t, struct timespec *);
int    sched_setparam(pid_t, const struct sched_param *);
int    sched_setscheduler(pid_t, int, const struct sched_param *);
int    sched_yield(void);

Inclusion of the <sched.h> header may make visible all symbols from the <time.h> header. 🫢 (sneaky little header crossover moment)

The following sections are informative.


πŸ¦‹ APPLICATION USAGE πŸ¦‹

None. πŸ’€ literally nothing. the void. the empty set. iconic behavior honestly.


πŸ“ RATIONALE πŸ“

None. πŸ’€ again!! nothing!! we love a low-effort section, periodt.


⭐ FUTURE DIRECTIONS ⭐

None. πŸ’€ three for three. it's a clean sweep bestie.


🌸 SEE ALSO 🌸

  • <sys_types.h>
  • <time.h>
  • The System Interfaces volume of POSIX.1‐2017: sched_get_priority_max(), sched_getparam(), sched_getscheduler(), sched_rr_get_interval(), sched_setparam(), sched_setscheduler(), sched_yield()

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

fr fr, if something looks cursed in here it's probably a formatting glitch from the conversion, not a vibe β€” go report it at that link πŸ’–

and that's the whole page bestie!! brought to you by IEEE/The Open Group, 2017, and yes it really does end with sched.h(0P) β€” slay πŸ’…βœ¨

πŸ“¦ where this page comes from