rte_flow_tcp_dir_param(3)

πŸ“¦ version 26.03, in nixos 26.05, nixpkgs unstable

πŸ’… rte_flow_tcp_dir_param(3) β€” bestie's guide to the TCP direction param struct

okay so this is a page straight out of the Library Functions Manual for DPDK, and it's all about the struct rte_flow_tcp_dir_param πŸŽ€. It's giving "one direction of a TCP conversation, fully annotated" and honestly it's kind of iconic. Let's get into it ✨


🌸 NAME

rte_flow_tcp_dir_param β€” the struct that holds the config params for each direction of a TCP connection, no cap 🫢


⭐ SYNOPSIS

#include <rte_flow.h>

πŸ¦‹ Data Fields

  • uint32_t scale:4
  • uint32_t close_initiated:1
  • uint32_t last_ack_seen:1
  • uint32_t data_unacked:1
  • uint32_t sent_end
  • uint32_t reply_end
  • uint32_t max_win
  • uint32_t max_ack

like... look at those little bitfields. :1 three times in a row?? the way that packs so tight, obsessed πŸ’–


✨ Detailed Description

⚠️ Warning β€” EXPERIMENTAL: this structure may change without prior notice. so like, don't get too attached bestie, it might ghost you 😭

Configuration parameters for each direction of a TCP connection. All fields should be in host byte order. If needed, the driver should convert all fields to network byte order if the HW needs them in that way. (HW being picky about byte order is such a mood πŸ™ˆ)

Definition at line 3989 of file rte_flow.h.


πŸ‘‘ Field Documentation

πŸ“ uint32_t scale

TCP window scaling factor. 0xF to disable it. yes, 0xF is literally the "nvm, turn it off" value πŸ’€

Definition at line 3991 of file rte_flow.h.

πŸŽ€ uint32_t close_initiated

The FIN was sent by this direction. like, this side said "k bye" first 🫑

Definition at line 3993 of file rte_flow.h.

🌈 uint32_t last_ack_seen

An ACK packet has been received by this side. so yes, they heard you, they're responding πŸ₯Ή

Definition at line 3995 of file rte_flow.h.

πŸ’œ uint32_t data_unacked

If set, it indicates that there is unacknowledged data for the packets sent from this direction. aka stuff you sent that nobody's confirmed yet. the "delivered βœ“ or read receipt??" of TCP fr fr 😭

Definition at line 4000 of file rte_flow.h.

🧚 uint32_t sent_end

Maximal value of sequence + payload length in sent packets (next ACK from the opposite direction). it's the high-water mark of what you've flung out there 🌊

Definition at line 4005 of file rte_flow.h.

πŸ”₯ uint32_t reply_end

Maximal value of (ACK + window size) in received packet + length over sent packet (maximal sequence could be sent). literally the furthest your sequence number could possibly go πŸ‘‘

Definition at line 4010 of file rte_flow.h.

🌸 uint32_t max_win

Maximal value of the actual window size in sent packets. biggest window they've advertised, highkey generous πŸ’…

Definition at line 4012 of file rte_flow.h.

⭐ uint32_t max_ack

Maximal value of ACK in sent packets. the highest ACK you've ever sent. periodt πŸ’–

Definition at line 4014 of file rte_flow.h.


🫢 Author

Generated automatically by Doxygen for DPDK from the source code. (so no human wrote this one, it's giving machine main character energy πŸ€–βœ¨)


that's the whole page bestie, hope the vibe check passed πŸ’…

cute lil sign-off: this was DPDK, Version 26.03.0 β€” page rte_flow_tcp_dir_param(3) β€” see you in the next one, mwah πŸ˜˜πŸ’–
πŸ“¦ where this page comes from