rte_gso_ctx(3)
β¨ rte_gso_ctx β¨
okay bestie, welcome to the rte_gso_ctx page π this one lives in section 3 of the manual (Library Functions Manual, for the record), and it's literally the whole mood board for GSO. get comfy π«Ά
πΈ NAME πΈ
rte_gso_ctx β no cap, that's the name π
π¦ SYNOPSIS π¦
#include <rte_gso.h>
β¨ Data Fields β¨
struct rte_mempool * direct_poolstruct rte_mempool * indirect_pooluint64_t flaguint32_t gso_typesuint16_t gso_size
π Detailed Description π
it's the GSO context structure, periodt. that's the whole vibe.
Defined at line 37 of file rte_gso.h.
π Field Documentation π
π struct rte_mempool* direct_pool
this is the MBUF pool you use to allocate direct buffers, and those are the ones storing packet headers for GSO segments. iconic header storage behavior π
Defined at line 38 of file rte_gso.h.
π§ struct rte_mempool* indirect_pool
and this one is the MBUF pool for allocating indirect buffers, which get used to locate packet payloads for GSO segments. lowkey the clever part: the indirect buffer doesn't contain any data, it just points to an offset within the packet to segment. it's giving "i know a guy" energy π«Ά
Defined at line 42 of file rte_gso.h.
β uint64_t flag
the flag that controls specific attributes of your output segments β like the type of IP ID generated (so, fixed or incremental). basically the little switch that decides how things get stamped β¨
Defined at line 48 of file rte_gso.h.
π uint32_t gso_types
the bit mask of required GSO types. the GSO library uses the same macros as the ones describing device TX offloading capabilities (that's the RTE_ETH_TX_OFFLOAD_*_TSO crew) for gso_types. iykyk πΈ
for example, if applications want to segment TCP/IPv4 packets, set RTE_ETH_TX_OFFLOAD_TCP_TSO in gso_types. see? simple, slay β¨
Defined at line 52 of file rte_gso.h.
π uint16_t gso_size
the maximum size of an output GSO segment β that means packet header and payload together, measured in bytes. and listen: it must exceed RTE_GSO_SEG_SIZE_MIN. not optional, not negotiable, bestie π
Defined at line 61 of file rte_gso.h.
π Author π
generated automatically by Doxygen for DPDK from the source code. not me being autogenerated and still serving looks π
aaaaand that's the whole page, babe π¦ this was DPDK, Version 25.11.3, fr fr β go forth and segment responsibly, mwah ππβ¨
π¦ 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