rte_ecpri_msg_rm_access(3)
π NAME π
rte_ecpri_msg_rm_access β bestie, this is a struct, and it's living its truth as the eCPRI Message Header of Type #4: Remote Memory Access. Yes ma'am. It's from rte_ecpri.h (DPDK, Library Functions Manual energy, we love to see it) and it's here to hold all the little header bits your Remote Memory Access messages need. Periodt. β¨
πΈ SYNOPSIS πΈ
#include <rte_ecpri.h>
π Data Fields π
uint32_t ele_id:16
uint32_t rr:4
uint32_t rw:4
uint32_t rma_id:8
uint8_t addr [6]
rte_be16_t length
π¦ Detailed Description π¦
eCPRI Message Header of Type #4: Remote Memory Access
Not me justβ¦ stating the vibe. It's a header struct. That's the whole job. And it's slaying at it. π
Definition at line 121 of file rte_ecpri.h.
π Field Documentation π
β uint32_t ele_id
Element ID
Definition at line 123 of file rte_ecpri.h.
π uint32_t rr
Req/Resp
Definition at line 124 of file rte_ecpri.h.
π uint32_t rw
Read/Write
Definition at line 125 of file rte_ecpri.h.
π«Ά uint32_t rma_id
Remote Memory Access ID
Definition at line 126 of file rte_ecpri.h.
π uint8_t addr[6]
48-bits address
Definition at line 133 of file rte_ecpri.h.
π§ rte_be16_t length
number of bytes
Definition at line 134 of file rte_ecpri.h.
π« Author π«
Generated automatically by Doxygen for DPDK from the source code.
Okay bestie, that's the whole page β and before you go, the iconic sign-off: this is DPDK, Version 25.11.3, from the Library Functions Manual set (rte_ecpri_msg_rm_access(3)). Go read your remote memory and be unbothered. π
πβ¨
π¦ where this page comes from
- ubuntu resolute: dpdk-doc 25.11.3-0ubuntu0.26.04.1 Β· BSD-3-Clause
- ubuntu stonking: dpdk-doc 25.11.3-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms