octep_vf_request_irqs(9)

✨ NAME ✨

okay so bestie, meet octep_vf_request_irqs — that’s octep_vf_request_irqs(9) from the Kernel API Manual 🫶. Its whole main-character job? Registering interrupt handlers. Periodt 💅.

🦋 SYNOPSIS 🦋

int octep_vf_request_irqs (struct octep_vf_device *oct );

🌸 ARGUMENTS 🌸

• oct — the Octeon device private data structure 💜. That’s the one and only argument, no cap.

💅 DESCRIPTION 💅

Lowkey the whole vibe: this function registers handlers for all the queue interrupts and all the non-queue interrupts 🔥. Every queue interrupt, every non-queue interrupt — that’s the assignment, fr fr.

🎀 RETURN 🎀

• 0 — slay ✨, on successful registration of all interrupt handlers.
• -1 — not slay 😭, on any error.

⭐ SEE ALSO ⭐

go read these next, iykyk 👑:

• Kernel file: ./drivers/net/ethernet/marvell/octeon_ep_vf/octep_vf_main.c
• octep_vf_alloc_ioq_vectors(9)
• octep_vf_free_ioq_vectors(9)
• octep_vf_enable_msix_range(9)
• octep_vf_disable_msix(9)
• octep_vf_ioq_intr_handler(9)
• octep_vf_free_irqs(9)
• octep_vf_setup_irqs(9)
• octep_vf_clean_irqs(9)
• octep_vf_update_pkt(9)
• octep_vf_enable_ioq_irq(9)
• octep_vf_napi_poll(9)
• octep_vf_napi_add(9)
• octep_vf_napi_delete(9)
• octep_vf_napi_enable(9)
• octep_vf_napi_disable(9)
• octep_vf_open(9)
• octep_vf_stop(9)
• octep_vf_iq_full_check(9)
• octep_vf_start_xmit(9)
• octep_vf_get_stats64(9)
• octep_vf_tx_timeout_task(9)
• octep_vf_tx_timeout(9)
• octep_vf_device_setup(9)
• octep_vf_device_cleanup(9)
• octep_vf_probe(9)
• octep_vf_remove(9)
• octep_vf_init_module(9)
• octep_vf_exit_module(9)

that’s the whole page, bestie 💖 from the Kernel API Manual, source/version ./drivers/net/ethernet/marvell..., dated October 2026, page octep_vf_request_irqs(9). bye 🫶