NODE_ID(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

🌸 NAME 🌸

rte_node_ip4_reassembly_cfg — bestie, this is the reassembly configure struct 💅 it's the lil bundle of fields you fill in so the IP4 reassembly node knows what's what. No cap.

✨ SYNOPSIS ✨

#include <rte_node_ip4_api.h>

🎀 Data Fields 🎀

  • struct rte_ip_frag_tbl * tbl
  • struct rte_ip_frag_death_row * dr
  • rte_node_t node_id

💖 Detailed Description 💖

Okay so picture this: it's the reassembly configure structure. That's the whole vibe. It's the struct you hand over when you're configuring reassembly — three fields, all baddies, all doing their job 🫶

See also: rte_node_ip4_reassembly_configure — literally go read that one too, it's the function that actually takes this struct, iykyk ✨

Definition at line 66 of file rte_node_ip4_api.h.

🦋 Field Documentation 🦋

struct rte_ip_frag_tbl* tbl

Reassembly fragmentation table — the table where all the fragments live. It's giving load-bearing, honestly 🔥

Definition at line 67 of file rte_node_ip4_api.h.

struct rte_ip_frag_death_row* dr

Reassembly deathrow table 😭💀 — yes that is genuinely the name, I didn't make it up. Iconic, dramatic, ominous. We love her.

Definition at line 69 of file rte_node_ip4_api.h.

rte_node_t node_id

Node identifier to configure — this is the one that says which node we're talking about. Main character selection energy, fr fr 👑

Definition at line 71 of file rte_node_ip4_api.h.

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. Not me, not you — the robot did it 🙈✨

And that's the page, bestie 🎀 it lives in the Library Functions Manual, section 3 (you probably clocked the truncated rte_node_i...ssembly_cfg(3) at the top and were like "what"), and it ships with DPDK, Version 26.03.0. Slay, go configure some reassembly 💜

📦 where this page comes from