bdx_tx_transmit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, this is bdx_tx_transmit(9) from the Kernel API Manual β€” the whole point is send packet to NIC. no cap, that's literally the name and the vibe.

✨ SYNOPSIS ✨

netdev_tx_t bdx_tx_transmit (struct sk_buff *skb , struct net_device
       *ndev );

πŸŽ€ ARGUMENTS πŸŽ€

  • skb β€” packet to send.
  • ndev β€” network device assigned to NIC.

Return codes, bestie:

  • NETDEV_TX_OK β€” everything ok. slay.
  • NETDEV_TX_BUSY β€” Cannot transmit packet, try later. Usually a bug, means queue start/stop flow control is broken in the driver.
Note: the driver must NOT put the skb in its DMA ring. literally do not do that.

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/net/ethernet/tehuti/tehuti.c.

Also the whole iconique friend group: bdx_fifo_init(9), bdx_fifo_free(9), bdx_link_changed(9), bdx_isr_napi(9), bdx_fw_load(9), bdx_hw_start(9), bdx_close(9), bdx_open(9), __bdx_vlan_rx_vid(9), bdx_vlan_rx_add_vid(9), bdx_vlan_rx_kill_vid(9), bdx_change_mtu(9), bdx_rx_init(9), bdx_rx_free_skbs(9), bdx_rx_free(9), bdx_rx_alloc_skbs(9), bdx_rx_receive(9), __bdx_tx_db_ptr_next(9), bdx_tx_db_inc_rptr(9), bdx_tx_db_inc_wptr(9), bdx_tx_db_init(9), bdx_tx_db_close(9), bdx_tx_map_skb(9), bdx_tx_space(9), bdx_tx_cleanup(9), bdx_tx_free_skbs(9), bdx_tx_push_desc(9), bdx_tx_push_desc_safe(9), bdx_probe(9), bdx_remove(9).


that's the whole vibe β€” source/version ./drivers/net/ethernet/tehuti, dated October 2026. bye bestie πŸ’–

πŸ“¦ where this page comes from