igb_set_inte...t_capability(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– igb_set_interrupt_capability(9) πŸ’–

okay bestie, this page is from the Kernel API Manual, and the header does that dramatic truncation thing: igb_set_inte...t_capability(9) β€” iykyk, it's giving mysterious ellipsis but it's literally the function below. ✨

🌸 NAME 🌸

igb_set_interrupt_capability β€” set MSI or MSI-X if supported. That's the whole vibe: MSI or MSI-X, but only if the hardware is down.

πŸ¦‹ SYNOPSIS πŸ¦‹

void igb_set_interrupt_capability (struct igb_adapter *adapter , bool msix );

Exact signature, no cap. Return type is void, so it is not handing you a value back. πŸ’…

πŸŽ€ ARGUMENTS πŸŽ€

  • adapter β€” the board private structure to initialize. This is the igb adapter bestie you're passing in.
  • msix β€” a boolean value of the MSIX capability. Basically the yes/no switch for MSI-X energy.

✨ DESCRIPTION ✨

It attempts to configure interrupts using the best available capabilities of the hardware and the kernel. So it's like, "what's the best interrupt setup we can pull off here?" and then it tries that. No extra promises β€” just the attempt. 🫢

πŸ’œ SEE ALSO πŸ’œ

Kernel file: ./drivers/net/ethernet/intel/igb/igb_main.c

The whole igb friend group is linked here, and every single one is getting their shoutout:

Okurrr, that's the page! πŸ’… Source/version: ./drivers/net/ethernet/intel/igb. Date: October 2026. Manual tag: igb_set_inte...t_capability(9). Bye bestie! 🫢

πŸ“¦ where this page comes from