rte_timer_status(3)
β¨ NAME β¨
rte_timer_status β bestie, this is the lil union that holds a timer's whole vibe: its state and which lcore owns it π
πΈ SYNOPSIS πΈ
#include <rte_timer.h>
π¦ Data Fields
uint32_t u32
π DESCRIPTION π
Okay so picture this: rte_timer_status is literally a union β like, one blob of memory that can wear two different fits π On one side you've got the state (which is one of stopped, pending, running, or config), and on the other side you've got the owner β the id of the lcore that owns the timer. Same space, different looks, that's the whole point, iykyk π
Fr fr, it's a union, so it's one thing at a time β not both at once. Don't come for me, that's just how unions work β¨
Definition at line 66 of file rte_timer.h.
π§ FIELD DOCUMENTATION π§
π uint16_t state
Stop, pending, running, config. That's the menu, bestie β those are your four options π
Definition at line 68 of file rte_timer.h.
β int16_t owner
The lcore that owns the timer. Like, whose timer is this? This one. π«Ά
Definition at line 69 of file rte_timer.h.
π uint32_t u32
To atomic-set status + owner. So you can slam the status and the owner in there atomically β iconic behaviour, no cap π₯
Definition at line 71 of file rte_timer.h.
π AUTHOR π
Generated automatically by Doxygen for DPDK from the source code. Not me writing it by hand, it's giving robot-built-and-that's-valid πβ¨
And that's the whole page, bestie β this one's from DPDK Version 26.03.0, brought to you by the rte_timer_status(3) manual page. Mwah, go slay your timers πππ¦
π¦ where this page comes from
- nixos 26.05: dpdk 26.03
- nixpkgs unstable: dpdk 26.03
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms