rte_ecpri_msg_bit_seq(3)

📦
version 25.11.3 · 9 versions
, in ubuntu resolute, ubuntu stonking

💖 rte_ecpri_msg_bit_seq 💖

okay bestie, welcome to the rte_ecpri_msg_bit_seq page — that's manual Library Functions Manual, section 3 (the "functions" girlies, iykyk). she's a struct, she's tiny, she's got exactly two fields, and she is lowkey carrying the whole Type #1 header situation. let's get into it 🎀

✨ NAME ✨

rte_ecpri_msg_bit_seq — the eCPRI Message Header of Type #1: Bit Sequence. that's the whole name, no extra crumbs, iconic behavior ✨

🌸 SYNOPSIS 🌸

#include <rte_ecpri.h>

🦋 Data Fields 🦋

  • rte_be16_t pc_id
  • rte_be16_t seq_id
two fields. that's it. she's a minimalist. 💅

💜 Detailed Description 💜

So this struct is the eCPRI Message Header of Type #1: Bit Sequence. that's literally the whole description bestie, no notes, no elaboration, the source just points at it and goes "yes, this one" 🫶

it lives at Definition at line 97 of file rte_ecpri.h. — so if ur tryna find her, line 97 of rte_ecpri.h, periodt.

⭐ Field Documentation ⭐

🍓 rte_be16_t pc_id

It's the Physical channel ID. physical. channel. ID. say it with me 📣

Definition at line 98 of file rte_ecpri.h.

🧚 rte_be16_t seq_id

And this one? the Sequence ID. keeping the sequence in sequence, as she should 💫

Definition at line 99 of file rte_ecpri.h.

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. — so not a human author, it's the Doxygen girlie doing her automated slay ✨ don't come for her, she's just the messenger 🎀

heads up bestie: this page was auto-generated from the source, so the descriptions are exactly as terse as they look. no hidden lore in here, fr fr 💀

and that's the whole page, we ate and left zero crumbs 🍽️💅 this was rte_ecpri_msg_bit_seq from DPDK, Version 25.11.3 — mwah, take care of her, bye bestie 🦋💖🌸

📦 where this page comes from