mlx5_irq_request_vector(9)

💖 NAME 💖

okay so bestie, welcome to mlx5_irq_request_vector(9) from the Kernel API Manual — this is the little function that requests one IRQ for an mlx5 device. iconic behavior, honestly ✨

🎀 SYNOPSIS 🎀

struct mlx5_irq * mlx5_irq_request_vector (struct mlx5_core_dev *dev ,
u16 cpu , u16 vecidx , struct cpu_rmap **rmap );

🌸 ARGUMENTS 🌸

• dev — the mlx5 device that is asking for the IRQ. it’s giving “main character device energy” 👑
• cpu — the CPU you want to bind the IRQ to. yes, one specific CPU. we’re being intentional 💅
• vecidx — the vector index to request an IRQ for. this is the lil index that says which vector we’re talking about 🎯
• rmap — pointer to reverse map pointer for completion interrupts. lowkey important pointer-to-a-pointer situation 🫶

🦋 DESCRIPTION 🦋

Each IRQ is bound to at most 1 CPU. not two, not a whole little CPU group chat — at most one, periodt 💀

This function requests one IRQ for the given vecidx. simple, focused, slay ✨

On success, it returns a pointer to the irq. if there’s an error, it returns an error pointer. no cap, that’s the whole return vibe 😭

bestie reminder: success = pointer to the irq, error = error pointer. don’t get it twisted 💖

🌈 SEE ALSO 🌈

• Kernel file: ./drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c
• mlx5_get_default_msix_vec_count(9)
• mlx5_set_msix_vec_count(9)
• mlx5_ctrl_irq_release(9)
• mlx5_ctrl_irq_request(9)
• mlx5_irq_request(9)
• mlx5_irq_release_vector(9)

xoxo, your Unix bestie 💋 — source/version line: ./drivers/net/ethernet/mellano..., date: October 2026, page: mlx5_irq_request_vector(9). mwah 🫶