STRUCT NFP_FLOWER_REPR_PRIV(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’ struct nfp_flower_repr_priv(9) πŸ’

okay so bestie, welcome to the Kernel API Manual and buckle up, because we're about to get intimately acquainted with struct nfp_flower_repr_priv β€” that's the Flower APP per-repr priv data and honestly? she's kind of a big deal πŸŽ€


✨ NAME ✨

struct nfp_flower_repr_priv β€” Flower APP per-repr priv data πŸ¦‹

lowkey the whole personality of this struct is "I hold the private data for one repr, and I hold it well" and we respect that fr fr πŸ’…


🌸 SYNOPSIS 🌸

struct nfp_flower_repr_priv {
    struct nfp_repr *nfp_repr;
    unsigned long lag_port_flags;
    bool mac_offloaded;
    u8 offloaded_mac_addr[ETH_ALEN];
    bool block_shared;
    struct list_head mac_list;
    struct nfp_fl_qos qos_table;
    bool on_bridge;
 };

look at her. eight members. not one of them skipped. she's giving organized ✨


πŸ’– Members πŸ’–

okay bestie, member-by-member breakdown, no cap, nothing left out:

  • nfp_repr β€” a back pointer to nfp_repr 🫢 like, she points right back home. it's giving "I know where I came from."
  • lag_port_flags β€” those extended port flags that record the lag state of the repr πŸ’€ an unsigned long, and it's keeping receipts on lag state, periodt.
  • mac_offloaded β€” a bool flag telling you a MAC address is offloaded for the repr ✨ true/false, icon status only.
  • offloaded_mac_addr β€” the actual MAC address that's been offloaded for the repr, stored as u8 offloaded_mac_addr[ETH_ALEN] 🌈 she's got the address. she's got the receipts.
  • block_shared β€” a bool flag saying whether the offload applies to shared blocks πŸ‘‘ that's it, that's the whole vibe check.
  • mac_list β€” a struct list_head list entry of reprs that share the same offloaded MAC 🧚 the group chat of reprs with the same MAC, and she's on it.
  • qos_table β€” a struct nfp_fl_qos with the stored info on filters implementing qos πŸŽ€ stored. info. on. filters. implementing. qos. slay.
  • on_bridge β€” a bool that indicates if the repr is attached to a bridge πŸŒ‰ attached or not attached, and now you know which.
ngl, every single one of these is a real member with real work to do β€” no filler, no extras, no invented fields. the struct is exactly the struct πŸ’œ

πŸ¦‹ SEE ALSO πŸ¦‹

go look at the Kernel file ./drivers/net/ethernet/netronome/nfp/flower/main.h β€” that's the source of truth, bestie πŸ“

and then the whole friend group, who all showed up to the party:

  • struct nfp_fl_tunnel_offloads(9)
  • struct nfp_tun_neigh_lag(9)
  • struct nfp_tun_neigh(9)
  • struct nfp_tun_neigh_ext(9)
  • struct nfp_tun_neigh_v4(9)
  • struct nfp_tun_neigh_v6(9)
  • struct nfp_neigh_entry(9)
  • struct nfp_predt_entry(9)
  • struct nfp_mtu_conf(9)
  • struct nfp_fl_lag(9)
  • struct nfp_fl_internal_ports(9)
  • struct nfp_flower_priv(9)
  • struct nfp_fl_qos(9)
  • struct nfp_flower_non_repr_priv(9)
  • struct nfp_ipv6_addr_entry(9)

iykyk πŸ’…βœ¨


okay and finally, the cute lil sign-off you came for: this page hails from ./drivers/net/ethernet/netrono... and it's dated October 2026, and it's literally <pink>struct nfp_flower_repr_priv(9)</pink> all the way down πŸ’– bye bestie, go read some headers πŸŽ€πŸ«Ά

πŸ“¦ where this page comes from