rte_ipv4_tuple(3)

πŸ’… NAME πŸ’…

rte_ipv4_tuple β€” okay bestie, this page is rte_ipv4_tuple(3), which is section 3, the Library Functions Manual corner of the world. Say hi to the lil declaration chillin' at line 65 of rte_thash.h. It's giving "small page, big opinions." πŸŽ€


✨ SYNOPSIS ✨

So the way that you even get access to this bad boy is:

#include <rte_thash.h>

That's it. That's the whole invite. No arguments, no flags, no return value drama. Just include the header and you're in the group chat. 🫢


🌸 DETAILED DESCRIPTION 🌸

Here's the tea, and it is the entire point of the page, so pay attention:

IPv4 tuple addresses and ports/sctp_tag have to be CPU byte order.

Like β€” CPU byte order, bestie. Not network byte order, not "whatever felt right in the moment," not "I'll fix it later." CPU byte order. If your addresses, your ports, or your sctp_tag are showing up in the wrong endianness, the hash is gonna be a whole mess and the vibe check will not be passed. 😭

And for the receipts, iykyk β€” this is Definition at line 65 of file rte_thash.h. Go look, it's right there. πŸ‘‘


πŸ‘‘ AUTHOR πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. Yes, a robot wrote it. A robot with impeccable documentation habits, honestly. It ate and left no crumbs. πŸ€–βœ¨


And that's the whole page, fr fr. This little beauty came to you courtesy of DPDK, Version 25.11.3, from the source code itself, and it's rte_ipv4_tuple(3) β€” so if you need it again, just ask your nearest man command. Slay. πŸ’–πŸ¦‹

πŸ“¦ where this page comes from