ice_setup_tc_cls_flower(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

ice_setup_tc_cls_flower(9) — flower classifier offloads. Okay so this is the Kernel API Manual page for ice_setup_tc_cls_flower, and it's literally the flower classifier offloads situation. No cap, bestie, we're about to walk through the args, the return value, and the whole SEE ALSO friend group. 💅✨

✨ SYNOPSIS ✨

int ice_setup_tc_cls_flower (struct ice_netdev_priv *np , struct
       net_device *filter_dev , struct flow_cls_offload *cls_flower , bool
       ingress );

This is the function signature, character for character, because we do not mess with the code. iykyk. 🦋

🫶 ARGUMENTS 🫶

Here's the vibe check on every argument, and yes, they are all iconic:

  • np — net device to configure. That's the thing you're setting up, periodt.
  • filter_dev — device on which filter is added. It's giving "where the filter lives" energy.
  • cls_flower — offload data. The flower classifier info goes here, bestie.
  • ingress — if the rule is added to an ingress block. This bool tells you that exact thing.

💖 RETURN 💖

0 if the flower was successfully added or deleted, negative error code otherwise. So like, 0 is the slay outcome; a negative error code is the "not me getting an error" outcome. 😭 Keep that in mind. fr fr.

🌈 SEE ALSO 🌈

Kernel file: ./drivers/net/ethernet/intel/ice/ice_main.c.

This list is long and lowkey iconic, so every single reference is here, in order, no skipping:

Source/version: ./drivers/net/ethernet/intel/ice — date: October 2026 — manual: ice_setup_tc_cls_flower(9). Bye bestie, go slay those flower classifier offloads! 🎀💖

📦 where this page comes from