rte_port_frag.h(3)

✨ rte_port_frag.h β€” the manual page, but make it cute ✨

okay bestie, grab your iced coffee because we're reading a Library Functions Manual page and it's giving "kernel-adjacent but make it fashion". The page you're holding is rte_port_frag.h(3), and no, I will not be normal about it πŸ’…


🌸 NAME 🌸

rte_port_frag.h β€” that's literally the whole name, she's lowkey mysterious like that 🫢


🌈 SYNOPSIS 🌈

#include <stdint.h>
#include 'rte_port.h'

πŸŽ€ Data Structures

  • struct rte_port_ring_reader_frag_params β€” yes queen, she's the struct

πŸ¦‹ Variables

  • struct rte_port_in_ops rte_port_ring_reader_ipv4_frag_ops
  • struct rte_port_in_ops rte_port_ring_reader_ipv6_frag_ops

πŸ’– Detailed Description πŸ’–

RTE Port for IPv4 Fragmentation

so the tea is this, bestie: this port is built on top of a pre-initialized single consumer rte_ring ✨

and the reason why? to minimize the amount of packets stored in the ring at any given time, the IP fragmentation functionality is executed on ring read operation β€” which is exactly why this port is implemented as an input port. ikyk 😌

and if you wanna write to that same ring? a regular ring_writer port can be created to write to the same ring. two ports, one ring, no drama 🫢

now the packets β€” let's break it down, no cap:

  • the packets written to the ring are either complete IP datagrams or jumbo frames (i.e. IP packets with length bigger than the provided MTU value) 🐘
  • the packets read from the ring are all non-jumbo frames πŸ‘‘
  • the complete IP datagrams written to the ring are not changed β€” she's perfect, leave her alone πŸ™…
  • the jumbo frames are fragmented into several IP packets with length less or equal to MTU βœ‚οΈβœ¨
Definition in file rte_port_frag.h.

⭐ Variable Documentation ⭐

🧚 struct rte_port_in_ops rte_port_ring_reader_ipv4_frag_ops [extern]

ring_reader_ipv4_frag port operations πŸ’œ

🧚 struct rte_port_in_ops rte_port_ring_reader_ipv6_frag_ops [extern]

ring_reader_ipv6_frag port operations πŸ’œ


🌟 Author 🌟

Generated automatically by Doxygen for DPDK from the source code. (yes, a robot wrote this, and honestly? she ate πŸ€–πŸ’…)


and that's the whole page bestie, we're done!! this was rte_port_frag.h(3) from DPDK Version 25.11.3 β€” mwah, go forth and fragment responsibly πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ«ΆπŸ”₯πŸ‘‘πŸŒˆβ­πŸ’€πŸ™ˆπŸ“πŸ§šπŸ’œ

πŸ“¦ where this page comes from