idpf_is_rdma_cap_ena(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– idpf_is_rdma_cap_ena(9) β€” the Kernel API Manual bestie edition πŸ’–

okay so you're deep in the idpf driver (that's the Intel Ethernet one, iykyk) and you need to know one tiny thing: is RDMA even a thing here? bestie, this function is literally the vibe check for that. it's giving "one job, does it well" πŸŽ€ β€” the whole page lives in the Kernel API Manual, and we're gonna walk through it together, no cap.


✨ NAME ✨

idpf_is_rdma_cap_ena β€” determine if RDMA is supported πŸ’…

like, that's it. that's the function. she checks, she tells you, she leaves. icon behavior.


🌸 SYNOPSIS 🌸

bool idpf_is_rdma_cap_ena (struct idpf_adapter *adapter );

look at her. one argument, returns a bool. clean, minimal, main character energy fr fr.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • adapter β€” the private data struct πŸ’– that's it, that's the whole description. she just wants her struct idpf_adapter * and she's happy. hand her the adapter and let her cook.

⭐ RETURN ⭐

  • true β€” RDMA capability is enabled ✨ slay, go off, RDMA is on
  • false β€” otherwise πŸ’€ no RDMA for you, but it's fine, we're fine, everything's fine

no exit statuses, no signals, no error codes to memorize β€” just a good old fashioned yes/no. the way that a bool return is lowkey the most peaceful thing in kernel land 🫢

real talk though: don't assume anything beyond what's written here. true = RDMA capability enabled, false = otherwise. periodt. πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

okay this is the part where the manpage goes absolutely feral and lists everything in the neighborhood. like, the entire idpf extended family showed up to the group chat 🌈. every single one, in order, exactly as the original spills them:

The kernel file it lives in:

  • Kernel file ./drivers/net/ethernet/intel/idpf/idpf.h

Structs & enums (the whole cast of characters):

  • struct idpf_mac_filter(9)
  • enum idpf_state(9)
  • enum idpf_flags(9)
  • enum idpf_cap_field(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)

And the function besties 🫢:

like... 42 cross-references. she said "you want lore? I'll give you LORE." πŸ”₯ obsessed, honestly. also note the cute mix of struct and enum prefixes β€” copy them exactly when you go looking, bestie, the man page girlies don't play about their (9) suffixes πŸ’…


🧚 sign-off 🧚

and that's the whole page! source lives at ./drivers/net/ethernet/intel/idpf, dated October 2026 πŸ“, and yes she's still repping the Kernel API Manual β€” the idpf_is_rdma_cap_ena(9) girlies stay winning. go check your capability flag and have the day you deserve πŸ’œβœ¨

πŸ“¦ where this page comes from