rte_lcore_usage(3)

💖 NAME 💖

rte_lcore_usage — the lil struct that spills the tea on how hard each lcore is working, bestie. It lives in the Library Functions Manual, section 3, so it's a library function page, periodt.

---

✨ SYNOPSIS ✨

#include <rte_lcore.h>

Data Fields

• uint64_t total_cycles
• uint64_t busy_cycles

---

🌸 Detailed Description 🌸

Okay so rte_lcore_usage is literally just lcore usage statistics. That's the whole vibe. It's the place where the numbers about a single lcore's life get kept. 💅

Lowkey iconic that a struct's whole personality is "here are the stats", and it serves it every time.

Definition at line 332 of file rte_lcore.h.

---

🎀 Field Documentation 🎀

uint64_t total_cycles

The total amount of time that the application has been running on this lcore, measured in TSC cycles. Like, the entire existence of the app on that core, sum total, no cap. ⭐

Definition at line 337 of file rte_lcore.h.

uint64_t busy_cycles

The amount of time the application was busy, handling some workload on this lcore, also in TSC cycles. So total_cycles is the whole story and busy_cycles is the "not me sitting pretty doing nothing" part. 🔥

Definition at line 342 of file rte_lcore.h.

---

🫶 Author 🫶

Generated automatically by Doxygen for DPDK from the source code. (Yeah, no human wrote this one, it's built different — literally. 🙈)

---

🧚 Both fields are uint64_t and both are counted in TSC cycles, so don't be out here comparing them to seconds, bestie. 💀

That's the whole page, you ate it fr fr. Stay slaying those lcores. 👑

This was DPDK Version 25.11.3, page rte_lcore_usage(3), brought to you by the group chat 💖 🦋 🎀