rte_eth_ip...dynfield_t(3)

🌸 NAME 🌸

rte_eth_ip_reassembly_dynfield_t β€” bestie, this is a struct, and she's the lil' dynamic-field bundle that carries your IP reassembly fragments around when things didn't go exactly to plan πŸ’–


✨ SYNOPSIS ✨

#include <rte_ethdev.h>

πŸŽ€ Data Fields

  • struct rte_mbuf * next_frag
  • uint16_t time_spent
  • uint16_t nb_frags

πŸ’… DETAILED DESCRIPTION πŸ’…

okay so here's the tea, bestie: if the IP reassembly offload fails, the packet gets updated with the dynamic flag RTE_MBUF_DYNFLAG_IP_REASSEMBLY_INCOMPLETE_NAME, and the packets get returned without alteration β€” like, nothing got touched, she's exactly how she came in. 🫢

Then your application can go retrieve the attached fragments using the mbuf dynamic field RTE_MBUF_DYNFIELD_IP_REASSEMBLY_NAME. That's the whole vibe. iykyk πŸ’«

Definition at line 5972 of file rte_ethdev.h.

πŸ¦‹ FIELD DOCUMENTATION πŸ¦‹

🌈 struct rte_mbuf* next_frag

Next fragment packet. Your application should fetch the dynamic field of each fragment until a NULL is received and nb_frags is 0. Like keep going until she says she's done, no cap ✨

Definition at line 5977 of file rte_ethdev.h.

🌈 uint16_t time_spent

Time spent (in ms) by the hardware just sitting there waiting for more fragments to show up. clock's ticking bestie ⏳

Definition at line 5979 of file rte_ethdev.h.

🌈 uint16_t nb_frags

Number of more fragments attached in mbuf dynamic fields. literally the count of how many besties are still in the group chat πŸ’€

Definition at line 5981 of file rte_ethdev.h.

πŸ‘‘ AUTHOR πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. (not me writing fanfic, the robots did it fr fr πŸ€–)


okay periodt, that's the whole page πŸ’œ this little cutie comes to you courtesy of DPDK, Version 25.11.3, and she's filed under the manual page rte_eth_ip...dynfield_t(3) from the Library Functions Manual β€” go slay, bestie πŸŽ€πŸŒΈβœ¨

πŸ“¦ where this page comes from