STRUCT DPSW_ACL_ENTRY_CFG(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ struct dpsw_acl_entry_cfg(9) β€” the ACL entry glow-up

okay so bestie, welcome to the Kernel API Manual ✨ this one's a tiny little struct but she's important β€” she's the ACL entry itself, the actual rule that gets checked. she's from dpsw.h in the freescale dpaa2 driver world, mmmkay? let's get into it πŸ’…


✨ NAME ✨

struct dpsw_acl_entry_cfg β€” an ACL entry. that's it. that's her. one entry in your access control list, living her best life πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

struct dpsw_acl_entry_cfg {
    u64 key_iova;
    struct dpsw_acl_result result;
    int precedence;
 };

look at her. three fields. iconic. not a single wasted line 🌸


πŸ‘‘ Members πŸ‘‘

  • key_iova β€” this is the I/O virtual address of DMA-able memory, and that memory is filled with your key πŸ—οΈ β€” but heads up bestie, only after you've called dpsw_acl_prepare_entry_cfg. so don't go reading it before that, okay? order matters, no cap.
  • result β€” a struct dpsw_acl_result, and this is literally the required action to take when this entry gets hit πŸ”₯ like, the entry matched, now what? that's what this field is for.
  • precedence β€” the precedence inside the ACL, and bestie, 0 is the lowest πŸ“‰ so if you want something to win, you gotta go higher. BUT β€” and this is the important part β€” this priority can not change during the lifetime of a Policy πŸ’€ periodt. it's locked in. and it's your responsibility as the user to space the priorities out according to the consequent rule additions you're planning. so like... plan ahead, okay? give yourself room to insert stuff later πŸ™ˆ
🫢 fr fr, read that precedence bit twice. a Policy's lifetime is a long time and you can't renumber later. that's a you problem, not a struct problem.

🌈 SEE ALSO 🌈

everything she's adjacent to in the kernel file ./drivers/net/ethernet/freescale/dpaa2/dpsw.h:

  • DPSW_OPT_FLOODING_DIS(9)
  • DPSW_OPT_MULTICAST_DIS(9)
  • DPSW_OPT_CTRL_IF_DIS(9)
  • enum dpsw_component_type(9)
  • enum dpsw_flooding_cfg(9)
  • enum dpsw_broadcast_cfg(9)
  • DPSW_IRQ_EVENT_LINK_CHANGED(9)
  • DPSW_IRQ_EVENT_ENDPOINT_CHANGED(9)
  • struct dpsw_irq_cfg(9)
  • struct dpsw_attr(9)
  • struct dpsw_ctrl_if_attr(9)
  • struct dpsw_ctrl_if_pools_cfg(9)
  • enum dpsw_action(9)
  • struct dpsw_link_cfg(9)
  • struct dpsw_link_state(9)
  • struct dpsw_tci_cfg(9)
  • enum dpsw_stp_state(9)
  • struct dpsw_stp_cfg(9)
  • enum dpsw_accepted_frames(9)
  • enum dpsw_counter(9)
  • struct dpsw_if_attr(9)
  • struct dpsw_vlan_cfg(9)
  • struct dpsw_vlan_if_cfg(9)
  • enum dpsw_fdb_entry_type(9)
  • struct dpsw_fdb_unicast_cfg(9)
  • struct fdb_dump_entry(9)
  • struct dpsw_fdb_multicast_cfg(9)
  • enum dpsw_learning_mode(9)
  • struct dpsw_fdb_attr(9)
  • struct dpsw_fdb_cfg(9)
  • enum dpsw_flood_type(9)
  • struct dpsw_acl_cfg(9)
  • struct dpsw_acl_if_cfg(9)
  • struct dpsw_acl_fields(9)
  • struct dpsw_acl_key(9)
  • enum dpsw_acl_action(9)
  • struct dpsw_acl_result(9)
  • enum dpsw_reflection_filter(9)
  • struct dpsw_reflection_cfg(9)
  • struct dpsw_lag_cfg(9)

that's a whole friend group honestly πŸ’–


aaaand that's the page!! πŸ¦‹ source path got truncated in the original footer as ./drivers/net/ethernet/freesca... and the date stamp is October 2026 β€” so big slay to the October 2026 crew who shipped this doc πŸ“…πŸ’œ mwah, go configure your ACLs responsibly bestie πŸ’…βœ¨

πŸ“¦ where this page comes from