netprio_prio(9)
π netprio_prio β¨
okay bestie, so we're looking at the netprio_prio page from the Kernel API Manual β yes, the section 9 one, the kernel-internals girlies know π«Ά β and honestly? it's giving "tiny function, big responsibility." let's get into it π
πΈ NAME πΈ
netprio_prio β returns the effective netprio of a cgroupβnet_device pair. that's the whole vibe. cgroup on one side, net_device on the other, and this function tells you the priority that actually applies to that pairing β¨
π SYNOPSIS π
u32 netprio_prio (struct cgroup_subsys_state *css , struct net_device
*dev );
not me obsessed with how it returns a u32, okay π₯
π¦ ARGUMENTS π¦
cssβ the css part of the target pair (it's astruct cgroup_subsys_state *, so it's a cgroup-subsystem-state situation π)devβ the net_device part of the target pair (astruct net_device *, the network-device half of the duo π)
literally a two-piece matching set. a pair. periodt π
π§ DESCRIPTION π§
so, real talk: this one should be called under RCU read or rtnl lock, no cap. that's the entire description. that's the tea π
β οΈ bestie please heed this one β "should be called under RCU read or rtnl lock" is a real technical caveat, not a suggestion to ignore π lock it up properly before you call, iykyk.
lowkey the shortest description ever but highkey it matters π
β SEE ALSO β
- Kernel file
./net/core/netprio_cgroup.c netprio_set_prio(9)β the sibling function, go say hi π
and that's the page, bestie, hope the vibe check passed π β¨
sign-off time π: this one came from ./net/core, dated October 2026, from the Kernel API Manual β and yes, the header up top and this footer at the bottom both say netprio_prio(9) because that's just how these pages roll πΈ i'm obsessed, bye π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms