rte_node_ip6_api.h(3)

📦
version 25.11.3 · 4 versions
, in ubuntu resolute, ubuntu stonking

💖 NAME 💖

rte_node_ip6_api.h — bestie, this is the DPDK header for doing the control-path stuff of the ip6_* nodes, and it lives in the Library Functions Manual (section 3, iykyk) 💅

✨ SYNOPSIS ✨

#include <rte_common.h>
#include <rte_compat.h>
#include <rte_fib6.h>
#include <rte_ip6.h>

🌸 Enumerations

enum rte_node_ip6_lookup_next { RTE_NODE_IP6_LOOKUP_NEXT_REWRITE,
    RTE_NODE_IP6_LOOKUP_NEXT_PKT_DROP }

🦋 Functions

__rte_experimental int rte_node_ip6_route_add (const struct
    rte_ipv6_addr *ip, uint8_t depth, uint16_t next_hop, enum
    rte_node_ip6_lookup_next next_node)
__rte_experimental int rte_node_ip6_rewrite_add (uint16_t next_hop,
    uint8_t *rewrite_data, uint8_t rewrite_len, uint16_t dst_port)
__rte_experimental int rte_node_ip6_fib_create (int socket, struct
    rte_fib6_conf *conf)
__rte_experimental int rte_node_ip6_fib_route_add (const struct
    rte_ipv6_addr *ip, uint8_t depth, uint16_t next_hop, enum
    rte_node_ip6_lookup_next next_node)

💜 Detailed Description 💜

Warning ⚠️ EXPERIMENTAL: literally every function in this file may be changed or removed without prior notice. Not me warning you twice. It's giving "use at your own risk, bestie" 😭

So this API lets you do the control path functions of the ip6_* nodes — think ip6_lookup, ip6_rewrite, all of them. The glow-up happens from the control side, and the data path just benefits. Periodt. 👑

Definition in file rte_node_ip6_api.h.

🎀 Enumeration Type Documentation 🎀

enum rte_node_ip6_lookup_next

IP6 lookup next nodes. Like, where do we go after the lookup? Choose your own adventure, bestie 💫

Enumerator

  • RTE_NODE_IP6_LOOKUP_NEXT_REWRITE — Rewrite node. Slay.
  • RTE_NODE_IP6_LOOKUP_NEXT_PKT_DROP — Packet drop node. RIP to that packet, fr fr 💀

Definition at line 30 of file rte_node_ip6_api.h.

💅 Function Documentation 💅

__rte_experimental int rte_node_ip6_route_add (const struct rte_ipv6_addr * ip, uint8_t depth, uint16_t next_hop, enum rte_node_ip6_lookup_next next_node)

Add IPv6 route to lookup table. Manifesting your route into existence ✨

Parameters

  • ip — IPv6 address of route to be added.
  • depth — Depth of the rule to be added.
  • next_hop — Next hop id of the rule result to be added.
  • next_node — Next node to redirect traffic to.

Returns

0 on success, negative otherwise.

__rte_experimental int rte_node_ip6_rewrite_add (uint16_t next_hop, uint8_t * rewrite_data, uint8_t rewrite_len, uint16_t dst_port)

Add a next hop's rewrite data. Giving that next hop a whole makeover 🫶

Parameters

  • next_hop — Next hop id to add rewrite data to.
  • rewrite_data — Rewrite data.
  • rewrite_len — Length of rewrite data.
  • dst_port — Destination port to redirect traffic to.

Returns

0 on success, negative otherwise.

__rte_experimental int rte_node_ip6_fib_create (int socket, struct rte_fib6_conf * conf)

Create ipv6 FIB. Building the whole thing from scratch, main character energy 🔥

Parameters

  • socket — NUMA socket for FIB memory allocation.
  • conf — Structure containing FIB configuration.

Returns

0 on success, negative otherwise.

__rte_experimental int rte_node_ip6_fib_route_add (const struct rte_ipv6_addr * ip, uint8_t depth, uint16_t next_hop, enum rte_node_ip6_lookup_next next_node)

Add IPv6 route to FIB. Same vibe as the lookup-table one above, but the FIB edition 🌈

Parameters

  • ip — IPv6 address of route to be added.
  • depth — Depth of the rule to be added.
  • next_hop — Next hop id of the rule result to be added.
  • next_node — Next node to redirect traffic to.

Returns

0 on success, negative otherwise.

🌟 Author 🌟

Generated automatically by Doxygen for DPDK from the source code. The robots wrote it, I just made it cute 💖

okay bestie that's the whole page 🎀 no cap, every flag, param and return value made it through the vibe check. this was DPDK, Version 25.11.3, from the rte_node_ip6_api.h(3) page — stay experimental, stay iconic, and don't forget to recompile 💅✨🦋

📦 where this page comes from