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