rte_ecpri_msg_bit_seq(3)

πŸ“¦ version 26.03, in nixos 26.05, nixpkgs unstable

πŸ’… rte_ecpri_msg_bit_seq β€” from the Library Functions Manual πŸŽ€

okay so bestie, sit down, hydrate, and let me tell you about rte_ecpri_msg_bit_seq ✨ that's the whole NAME section btw, no long dramatic subtitle, that's just... it. That's the function/struct we're stanning today.


🌸 SYNOPSIS 🌸

Pull it in like this, exactly like this, no cap:

#include <rte_ecpri.h>

πŸ’– Data Fields

  • rte_be16_t pc_id β€” the physical channel ID 🫢
  • rte_be16_t seq_id β€” the sequence ID ⭐

That's the cast of characters. Two fields. Iconic, minimal, main character energy.


πŸ¦‹ Detailed Description πŸ¦‹

It's the eCPRI Message Header of Type #1: Bit Sequence πŸ’… that's literally what it is, that's the whole vibe.

Definition at line 97 of file rte_ecpri.h β€” bookmark that, bestie, iykyk πŸ“Œ


πŸ”₯ Field Documentation πŸ”₯

rte_be16_t pc_id

Physical channel ID ✨ (yes that's the entire description, she's a woman of few words and honestly? respect.)

Definition at line 98 of file rte_ecpri.h πŸŽ€

rte_be16_t seq_id

Sequence ID πŸ’« (again: short, sweet, to the point.)

Definition at line 99 of file rte_ecpri.h πŸ¦‹


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code πŸ€–πŸ’– so like, no human wrote this one, the robot did it, and it ate, honestly.


ngl there aren't any options, arguments, env vars, exit statuses or SEE ALSOs on this page β€” it's a lil struct page and she said "that's it, that's the tea" πŸ“ don't come for me, I checked, the facts are all here.

k byeee πŸ’œ this lil page came to you from DPDK, Version 26.03.0 β€” mwah, catch you in the next manpage, bestie πŸŒˆπŸ’…βœ¨

πŸ“¦ where this page comes from