rte_gso_ctx(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

💅 rte_gso_ctx — the manual page, but make it make sense

okay so bestie, welcome to the rte_gso_ctx(3) page from the DPDK Library Functions Manual ✨ this is a struct page, so it's giving "reference card" energy rather than "story time" — but we're gonna make it cute anyway 🎀

🌸 NAME 🌸

rte_gso_ctx — literally the GSO context structure, that's her name, that's her whole brand 👑

✨ SYNOPSIS ✨

#include <rte_gso.h>

🦋 Data Fields

  • struct rte_mempool * direct_pool
  • struct rte_mempool * indirect_pool
  • uint64_t flag
  • uint32_t gso_types
  • uint16_t gso_size

💖 DETAILED DESCRIPTION 💖

So this is the GSO context structure, periodt. That's the vibe. 🫶

Fun lil fact for the group chat: her definition lives at line 37 of file rte_gso.h — iconic address honestly 📍

👑 FIELD DOCUMENTATION 👑

🧺 struct rte_mempool* direct_pool

This is the MBUF pool for allocating direct buffers, and those direct buffers are the ones used to store packet headers for GSO segments — like, they're holding the lil header fits, no cap 💅

Located at line 38 of file rte_gso.h ✨

🎀 struct rte_mempool* indirect_pool

And this one is the MBUF pool for allocating indirect buffers, used to locate the packet payloads for GSO segments. The tea here 🍵: the indirect buffer doesn't contain any data — it literally just points to an offset within the packet to segment. It's giving "I know a guy" energy, not "I am the guy" energy 😭

Located at line 42 of file rte_gso.h ✨

🚩 uint64_t flag

A flag that controls specific attributes of output segments — for example, the type of IP ID generated (i.e. fixed or incremental). So yeah, she's the one making the ~stylistic choices~ 🔥

Located at line 48 of file rte_gso.h ✨

🌈 uint32_t gso_types

The bit mask of required GSO types. And here's the key lore 👀: the GSO library uses the same macros as that of describing device TX offloading capabilities (i.e. RTE_ETH_TX_OFFLOAD_*_TSO) for gso_types.

For example — and this is the moment, bestie — if applications want to segment TCP/IPv4 packets, set RTE_ETH_TX_OFFLOAD_TCP_TSO in gso_types. Easy. Slay. ✅

Located at line 52 of file rte_gso.h ✨

📏 uint16_t gso_size

The maximum size of an output GSO segment, including packet header and payload, measured in bytes.

⚠️ Bestie, listen to me: it must exceed RTE_GSO_SEG_SIZE_MIN. This is not a suggestion, this is the rule, fr fr 🙈

Located at line 61 of file rte_gso.h ✨

🧚 AUTHOR 🧚

Generated automatically by Doxygen for DPDK from the source code 🤖💖 (yes, the robot wrote it, we just gave it a personality)

and that's the whole page, bestie — tysm for reading 🫶 This lil masterpiece is from DPDK, Version 26.03.0, dated rte_gso_ctx(3) era energy — catch you on the next manpage, mwah 💋✨🎀

📦 where this page comes from