wx_alloc_rx_buffers(9)

✨ NAME ✨

This is wx_alloc_rx_buffers(9), straight outta the Kernel API Manual, bestie, and it's here to replace used receive buffers 💅

wx_alloc_rx_buffers — replace used receive buffers. That's the whole vibe: used ones out, fresh ones in, no cap ✨

💻 SYNOPSIS 💻

Here's the exact signature, don't freestyle it:

void wx_alloc_rx_buffers (struct wx_ring *rx_ring , u16 cleaned_count );

That void up front means no return value comes back, periodt 🫶

🎀 ARGUMENTS 🎀

Two arguments, both important, both giving main character energy:

• rx_ring — ring to place buffers on. Like, the literal ring where these buffers are getting placed, bestie 🦋
• cleaned_count — number of buffers to replace. How many buffers we're swapping in, fr fr 💖

🔗 SEE ALSO 🔗

Okay, the lore continues here — go read the kernel file and the whole friend group:

• Kernel file: ./drivers/net/ethernet/wangxun/libwx/wx_lib.c
• wx_is_non_eop(9)
• wx_cleanup_headers(9)
• wx_rx_checksum(9)
• wx_process_skb_fields(9)
• wx_clean_rx_irq(9)
• wx_clean_tx_irq(9)
• wx_poll(9)
• wx_set_rss_queues(9)
• wx_acquire_msix_vectors(9)
• wx_set_interrupt_capability(9)
• wx_cache_ring_rss(9)
• wx_alloc_q_vector(9)
• wx_free_q_vector(9)
• wx_alloc_q_vectors(9)
• wx_free_q_vectors(9)
• wx_clear_interrupt_scheme(9)
• wx_setup_isb_resources(9)
• wx_free_isb_resources(9)
• wx_set_ivar(9)
• wx_write_eitr(9)
• wx_configure_vectors(9)
• wx_clean_rx_ring(9)
• wx_clean_all_rx_rings(9)
• wx_free_rx_resources(9)
• wx_free_all_rx_resources(9)
• wx_clean_tx_ring(9)
• wx_clean_all_tx_rings(9)
• wx_free_tx_resources(9)
• wx_free_all_tx_resources(9)
• wx_setup_rx_resources(9)
• wx_setup_all_rx_resources(9)
• wx_setup_tx_resources(9)
• wx_setup_all_tx_resources(9)
• wx_get_stats64(9)

Okay that's the page, bestie 🎀 The source/version vibes come from ./drivers/net/ethernet/wangxun..., the date on deck is October 2026, and the page name again is wx_alloc_rx_buffers(9) 💖✨