rte_gro_param(3)
π NAME π
rte_gro_param β bestie, this is a struct, okay? Not a function, not a vibe, a literal struct π
It lives in the DPDK library functions crew, and it's the little parameter bag that GRO stuff runs on. Say hi π«Ά
β¨ SYNOPSIS β¨
#include <rte_gro.h>
π Data Fields
uint64_t gro_typesuint16_t max_flow_numuint16_t max_item_per_flowuint16_t socket_id
πΈ DETAILED DESCRIPTION πΈ
Okay so picture this: it's a struct used to create GRO context objects, or used to pass application-determined parameters into rte_gro_reassemble_burst(). Both jobs, one iconic little struct. Multi-hyphenate behavior fr fr β¨
Definition at line 49 of file rte_gro.h. π
π FIELD DOCUMENTATION π
π uint64_t gro_types
The desired GRO types. That's the whole vibe β you tell it which ones you want, it does the thing π«
Definition at line 50 of file rte_gro.h.
π uint16_t max_flow_num
Max flow number. The ceiling on how many flows we're dealing with, no cap on ambition though π€
Definition at line 52 of file rte_gro.h.
π uint16_t max_item_per_flow
Max packet number per flow. So like, per flow, this many packets max. Periodt π¦
Definition at line 54 of file rte_gro.h.
π uint16_t socket_id
Socket index for allocating GRO related data structures, like reassembly tables. And here's the tea, bestie: when you use rte_gro_reassemble_burst(), applications don't need to set this value. Like, genuinely, leave it, it's fine π
Definition at line 56 of file rte_gro.h.
π AUTHOR π
Generated automatically by Doxygen for DPDK from the source code. Not me hand-writing it, the robots did it, and honestly? They ate π€β¨
okay that's the whole page bestie, mwah π this was the rte_gro_param(3) manual page from DPDK Version 25.11.3 β go forth and reassemble responsibly, ily π¦π
π¦ 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