e1000_clean_rx_irq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

e1000_clean_rx_irq(9) πŸ‘‘

okay bestie, welcome to the Kernel API Manual page for e1000_clean_rx_irq β€” manual name folded in right here like a little name tag, because we're cute like that 🫢.


πŸ’– NAME πŸ’–

e1000_clean_rx_irq β€” Send received data up the network stack. That's the name vibe: received data goes up the network stack, and this function is the main character doing it. πŸ’…


🌸 SYNOPSIS 🌸

here's the signature, exactly as it appears β€” no edits, no remix, no cap:

bool e1000_clean_rx_irq (struct e1000_ring *rx_ring , int *work_done , int work_to_do );

πŸŽ€ ARGUMENTS πŸŽ€

  • rx_ring β€” Rx descriptor ring; the ring where the received descriptors live. like the receipt stack for the Rx side 🧾
  • work_done β€” output parameter for indicating completed work; this is where the completed-work info goes.
  • work_to_do β€” how many packets we can clean; the packet-cleaning limit.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so the return value is literally the whole point: it indicates whether actual cleaning was done. and there is no guarantee that everything was cleaned β€” not everything, not automatically, don't assume 😭. it's giving "yes, some actual cleaning happened" energy, not "the whole ring is spotless," iykyk.


πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./drivers/net/ethernet/intel/e1000e/netdev.c

and the whole squad β€” every (9) bestie, no omissions, no cap πŸ’…:

__ew32_prepare(9), e1000_regdump(9), e1000e_dump(9),
e1000_desc_unused(9), e1000e_systim_to_hwtstamp(9),
e1000e_rx_hwtstamp(9), e1000_receive_skb(9), e1000_rx_checksum(9),
e1000_alloc_rx_buffers(9), e1000_alloc_rx_buffers_ps(9),
e1000_alloc_jumbo_rx_buffers(9), e1000e_tx_hwtstamp_work(9),
e1000_clean_tx_irq(9), e1000_clean_rx_irq_ps(9),
e1000_clean_jumbo_rx_irq(9), e1000_clean_rx_ring(9), e1000_intr_msi(9),
e1000_intr(9), e1000_configure_msix(9),
e1000e_set_interrupt_capability(9), e1000_request_msix(9),
e1000_request_irq(9), e1000_irq_disable(9), e1000_irq_enable(9),
e1000e_get_hw_control(9), e1000e_release_hw_control(9),
e1000_alloc_ring_dma(9), e1000e_setup_tx_resources(9),
e1000e_setup_rx_resources(9), e1000_clean_tx_ring(9),
e1000e_free_tx_resources(9), e1000e_free_rx_resources(9),
e1000_update_itr(9), e1000e_write_itr(9), e1000_alloc_queues(9),
e1000e_poll(9), e1000e_vlan_filter_disable(9),
e1000e_vlan_filter_enable(9), e1000e_vlan_strip_disable(9),
e1000e_vlan_strip_enable(9), e1000_configure_tx(9), e1000_setup_rctl(9),
e1000_configure_rx(9), e1000e_write_mc_addr_list(9),
e1000e_write_uc_addr_list(9), e1000e_set_rx_mode(9),
e1000e_get_base_timinca(9), e1000e_config_hwtstamp(9),
e1000_configure(9), e1000e_power_up_phy(9), e1000_power_down_phy(9),
e1000_flush_tx_ring(9), e1000_flush_rx_ring(9),
e1000_flush_desc_rings(9), e1000e_systim_reset(9), e1000e_reset(9),
e1000e_trigger_lsc(9), e1000e_down(9), e1000e_sanitize_systim(9),
e1000e_read_systim(9), e1000e_cyclecounter_read(9), e1000_sw_init(9),
e1000_intr_msi_test(9), e1000_test_msi_interrupt(9), e1000_test_msi(9),
e1000e_open(9), e1000e_close(9), e1000_set_mac(9),
e1000e_update_phy_task(9), e1000_update_phy_info(9),
e1000e_update_phy_stats(9), e1000e_update_stats(9),
e1000_phy_read_status(9), e1000_watchdog(9), e1000_tx_timeout(9),
e1000e_get_stats64(9), e1000_change_mtu(9), e1000e_hwtstamp_set(9),
__e1000e_disable_aspm(9), e1000e_disable_aspm(9),
e1000e_disable_aspm_locked(9), e1000_netpoll(9),
e1000_io_error_detected(9), e1000_io_slot_reset(9), e1000_io_resume(9),
e1000_probe(9), e1000_remove(9), e1000_init_module(9),
e1000_exit_module(9)

and that's the page, bestie! footer check for the girlies: source/version ./drivers/net/ethernet/intel/e..., date October 2026, and the page is e1000_clean_rx_irq(9) β€” slay, periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from