ENUM IDPF_CAP_FIELD(9)

💅 enum idpf_cap_field — kernel API manual, bestie edition 🎀

okay so this page is all about enum idpf_cap_field from the Kernel API Manual, and honestly? it's giving "tiny enum, big responsibility" energy. sit down, grab a strawberry 🍓, and let's get into it.

---

✨ NAME ✨

enum idpf_cap_field — the offsets into the capabilities struct for specific caps. literally just index positions, but make it fashion 💅

---

🦋 SYNOPSIS 🦋

enum idpf_cap_field {
    IDPF_BASE_CAPS ,
    IDPF_CSUM_CAPS ,
    IDPF_SEG_CAPS ,
    IDPF_RSS_CAPS ,
    IDPF_HSPLIT_CAPS ,
    IDPF_RSC_CAPS ,
    IDPF_OTHER_CAPS

};

look at her. seven constants. no notes. 👑

---

🌸 Constants 🌸

one bullet per cap, no cap 🧢 — here's what each one means:

• IDPF_BASE_CAPS — the generic base capabilities. the main character of cap sets, tbh.
• IDPF_CSUM_CAPS — checksum offload capabilities. she's doing math so you don't have to ✨
• IDPF_SEG_CAPS — segmentation offload capabilities. chopping packets into lil pieces, iconic behavior.
• IDPF_RSS_CAPS — RSS offload capabilities. spreading the love (and the queues) around 💖
• IDPF_HSPLIT_CAPS — Header split capabilities. note the capital H, that's just how the manpage wrote it, we respect it 🫶
• IDPF_RSC_CAPS — RSC offload capabilities. receiving in bulk, lowkey efficient.
• IDPF_OTHER_CAPS — miscellaneous offloads. the catch-all. the "and friends" of the group chat 🙈

---

💜 Description 💜

so here's the vibe check: you use this enum when you're checking for a specific capability flag. and the reason you gotta is genuinely important — different capability sets are not mutually exclusive numerically, so the numbers can overlap and collide and generally be messy 😭. that means the caller must specify which type of capability they're checking for. no guessing, no vibes-based indexing. you say which set, periodt. 🔥

---

🌈 SEE ALSO 🌈

the whole friend group, in source order — Kernel file ./drivers/net/ethernet/intel/idpf/idpf.h plus:

• struct idpf_mac_filter(9)
• enum idpf_state(9)
• enum idpf_flags(9)
• enum idpf_vport_state(9)
• struct idpf_netdev_priv(9)
• struct idpf_reset_reg(9)
• struct idpf_vport_max_q(9)
• struct idpf_reg_ops(9)
• struct idpf_dev_ops(9)
• enum idpf_vport_reset_cause(9)
• enum idpf_vport_flags(9)
• struct idpf_tstamp_stats(9)
• struct idpf_q_vec_rsrc(9)
• struct idpf_vport(9)
• enum idpf_user_flags(9)
• struct idpf_rss_data(9)
• struct idpf_q_coalesce(9)
• struct idpf_vport_user_config_data(9)
• enum idpf_vport_config_flags(9)
• struct idpf_avail_queue_info(9)
• struct idpf_vector_info(9)
• struct idpf_vector_lifo(9)
• struct idpf_queue_id_reg_chunk(9)
• struct idpf_queue_id_reg_info(9)
• struct idpf_vport_config(9)
• struct idpf_adapter(9)
• idpf_is_queue_model_split(9)
• idpf_is_rdma_cap_ena(9)
• idpf_get_reserved_vecs(9)
• idpf_get_reserved_rdma_vecs(9)
• idpf_get_default_vports(9)
• idpf_get_max_vports(9)
• idpf_get_max_tx_bufs(9)
• idpf_get_min_tx_pkt_len(9)
• idpf_is_reset_detected(9)
• idpf_is_reset_in_prog(9)
• idpf_netdev_to_vport(9)
• idpf_netdev_to_adapter(9)
• idpf_is_feature_ena(9)
• idpf_get_max_tx_hdr_size(9)
• idpf_vport_ctrl_lock(9)
• idpf_vport_ctrl_unlock(9)

---

lowkey a whole ecosystem in here. go read the neighbors, bestie, iykyk 💀

---

and that's the page!! 🫶 source is ./drivers/net/ethernet/intel/idpf and the version is dated October 2026 — so yeah, she's from the future, we stan a time traveler. bye bestie, slay your capability checks, and remember: always name your cap set ✨👑💖