ixgbevf_write_eitr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so bestie, welcome to the ixgbevf_write_eitr(9) page β€” yes, that's the man page name, and it's straight out of the Kernel API Manual, so you know it's official πŸ’…

ixgbevf_write_eitr β€” write VTEITR register in hardware specific way πŸŽ€

like, that's the whole job. it writes the VTEITR register, but in a hardware specific way, because of course the hardware has opinions πŸ™ˆ


🌸 SYNOPSIS 🌸

void ixgbevf_write_eitr (struct ixgbevf_q_vector *q_vector );

returns void, takes one arg, no drama, no return value, she just does her thing ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • q_vector β€” structure containing interrupt and ring information. that's it, that's the whole vibe check: it's the struct that holds the interrupt info and the ring info, all bundled up together 🫢

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file herself lives at ./drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c β€” go read her, she's iconic πŸ“–

and now the entire friend group, no cap, every single one:

ixgbevf_set_ivar(9), ixgbevf_tx_timeout(9), ixgbevf_clean_tx_irq(9), ixgbevf_rx_skb(9), ixgbevf_rx_checksum(9), ixgbevf_process_skb_fields(9), ixgbevf_is_non_eop(9), ixgbevf_alloc_rx_buffers(9), ixgbevf_cleanup_headers(9), ixgbevf_reuse_rx_page(9), ixgbevf_add_rx_frag(9), ixgbevf_poll(9), ixgbevf_configure_msix(9), ixgbevf_update_itr(9), ixgbevf_msix_clean_rings(9), ixgbevf_request_msix_irqs(9), ixgbevf_request_irq(9), ixgbevf_irq_disable(9), ixgbevf_irq_enable(9), ixgbevf_configure_tx_ring(9), ixgbevf_configure_tx(9), ixgbevf_init_rss_key(9), ixgbevf_configure_rx(9), ixgbevf_set_rx_mode(9), ixgbevf_set_features(9), ixgbevf_clean_rx_ring(9), ixgbevf_clean_tx_ring(9), ixgbevf_clean_all_rx_rings(9), ixgbevf_clean_all_tx_rings(9), ixgbevf_set_num_queues(9), ixgbevf_set_interrupt_capability(9), ixgbevf_alloc_q_vector(9), ixgbevf_free_q_vector(9), ixgbevf_alloc_q_vectors(9), ixgbevf_free_q_vectors(9), ixgbevf_reset_interrupt_capability(9), ixgbevf_init_interrupt_scheme(9), ixgbevf_clear_interrupt_scheme(9), ixgbevf_sw_init(9), ixgbevf_update_stats(9), ixgbevf_service_timer(9), ixgbevf_check_hang_subtask(9), ixgbevf_watchdog_update_link(9), ixgbevf_watchdog_link_is_up(9), ixgbevf_watchdog_link_is_down(9), ixgbevf_watchdog_subtask(9), ixgbevf_service_task(9), ixgbevf_free_tx_resources(9), ixgbevf_free_all_tx_resources(9), ixgbevf_setup_tx_resources(9), ixgbevf_setup_all_tx_resources(9), ixgbevf_setup_rx_resources(9), ixgbevf_setup_all_rx_resources(9), ixgbevf_free_rx_resources(9), ixgbevf_free_all_rx_resources(9), ixgbevf_open(9), ixgbevf_close_suspend(9), ixgbevf_close(9), ixgbevf_set_mac(9), ixgbevf_change_mtu(9), ixgbevf_probe(9), ixgbevf_remove(9), ixgbevf_io_error_detected(9), ixgbevf_io_slot_reset(9), ixgbevf_io_resume(9), ixgbevf_init_module(9), ixgbevf_exit_module(9), ixgbevf_get_hw_dev_name(9)

like... that's the whole extended universe, fr fr 🫢

bestie note: that list is long, and that's on purpose β€” it's the real reference list, so don't skip a single one if you're chaining through the driver. no gatekeeping here πŸ’–

okay so this page is sourced from ./drivers/net/ethernet/intel/i... (that's the truncated source path, we love a cliffhanger 😭) and it's dated October 2026 β€” so mark your calendars bestie, and go write that VTEITR register the hardware-specific way πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from