SCHED_GET_PRIORITY_MAX(3P)

πŸ’– sched_get_priority_max(3P) β€” POSIX Programmer's Manual πŸ’–

okay bestie, welcome to the POSIX Programmer's Manual, page SCHED_GET_PRIORITY_MAX(3P). before we even start, real talk:

PROLOG heads-up: this manual page is part of the POSIX Programmer's Manual. the Linux implementation of this interface may differ (so go consult the corresponding Linux manual page for the deets on Linux behavior), or honestly the interface may not be implemented on Linux at all. no cap. 🫢

✨ NAME ✨

sched_get_priority_max, sched_get_priority_min β€” get priority limits (REALTIME) πŸ”₯


πŸŽ€ SYNOPSIS πŸŽ€

#include <sched.h>

int sched_get_priority_max(int policy);
int sched_get_priority_min(int policy);

πŸ’… DESCRIPTION πŸ’…

so like, sched_get_priority_max() and sched_get_priority_min() shall return the appropriate maximum or minimum, respectively, for the scheduling policy specified by policy. that's it, that's the whole vibe. 🌈

and the value of policy shall be one of the scheduling policy values defined in <sched.h>. periodt. πŸ“Œ


πŸ¦‹ RETURN VALUE πŸ¦‹

if it's successful, sched_get_priority_max() and sched_get_priority_min() shall return the appropriate maximum or minimum values, respectively. slay. ✨

if it's unsuccessful?? they shall return a value of -1 and set errno to indicate the error. not the moment bestie 😭


πŸ“ ERRORS πŸ“

the sched_get_priority_max() and sched_get_priority_min() functions shall fail if:

  • EINVAL β€” the value of the policy parameter does not represent a defined scheduling policy. like, that policy is not invited to the function πŸ’€
heads up: the following sections are informative. (so, vibe only, no rules here πŸ’œ)

🌸 EXAMPLES 🌸

None. πŸ™ˆ (yes literally, there are none, moving on bestie)


🧚 APPLICATION USAGE 🧚

None. πŸ’œ


πŸ‘‘ RATIONALE πŸ‘‘

None. πŸ’…


⭐ FUTURE DIRECTIONS ⭐

None. πŸŽ€


πŸ”₯ SEE ALSO πŸ”₯

  • sched_getparam()
  • sched_setparam()
  • sched_getscheduler()
  • sched_rr_get_interval()
  • sched_setscheduler()

also the Base Definitions volume of POSIX.1‐2017, <sched.h> πŸ“š


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. (read: the original is the main character, this one is the cover 🫢) 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 .


and that's the whole page, bestie!! πŸ’…βœ¨ brought to you by IEEE/The Open Group, 2017 β€” mwah, go read your scheduling policies responsibly πŸŽ€πŸ¦‹πŸ’–

πŸ“¦ where this page comes from