fm10k_mbx_write_copy(9)
π fm10k_mbx_write_copy(9) β or, like, the Kernel API Manual page you didn't know you needed
okay bestie, buckle up, because this is a page out of the Kernel API Manual and honestly it's kind of a glow-up moment for the Tx FIFO π
β¨ NAME β¨
fm10k_mbx_write_copy β the function that pulls data off of the Tx FIFO and places it in mbmem π
πΈ SYNOPSIS πΈ
void fm10k_mbx_write_copy (struct fm10k_hw *hw , struct fm10k_mbx_info
*mbx );
π ARGUMENTS π
hwβ pointer to the hardware structure π₯οΈ like, the actual vibes of the siliconmbxβ pointer to the mailbox π¬ the whole main character of this function, no cap
π« DESCRIPTION π«
so the way this works β¨ β this function will take a section of the Tx FIFO and copy it straight into the mailbox memory. iconic behavior honestly.
the offset in mbmem is based on the lower bits of the tail π― and len determines the length to copy. that's it, that's the whole lore π¦
lowkey obsessed with how tidy that is β tail bits in, length says how much, data lands in mbmem. periodt π
π SEE ALSO π
first up, the kernel file itself, right here:
./drivers/net/ethernet/intel/fm10k/fm10k_mbx.c
and now the whole group chat of related functions, fr fr π«Ά β every single one of them:
fm10k_fifo_init(9)fm10k_fifo_used(9)fm10k_fifo_unused(9)fm10k_fifo_empty(9)fm10k_fifo_head_offset(9)fm10k_fifo_tail_offset(9)fm10k_fifo_head_len(9)fm10k_fifo_head_drop(9)fm10k_fifo_drop_all(9)fm10k_mbx_index_len(9)fm10k_mbx_tail_add(9)fm10k_mbx_tail_sub(9)fm10k_mbx_head_add(9)fm10k_mbx_head_sub(9)fm10k_mbx_pushed_tail_len(9)fm10k_fifo_write_copy(9)fm10k_fifo_enqueue(9)fm10k_mbx_validate_msg_size(9)fm10k_mbx_pull_head(9)fm10k_mbx_read_copy(9)fm10k_mbx_push_tail(9)fm10k_crc_16b(9)fm10k_fifo_crc(9)fm10k_mbx_update_local_crc(9)fm10k_mbx_verify_remote_crc(9)fm10k_mbx_rx_ready(9)fm10k_mbx_tx_ready(9)fm10k_mbx_tx_complete(9)fm10k_mbx_dequeue_rx(9)fm10k_mbx_enqueue_tx(9)fm10k_mbx_read(9)fm10k_mbx_write(9)fm10k_mbx_create_connect_hdr(9)fm10k_mbx_create_data_hdr(9)fm10k_mbx_create_disconnect_hdr(9)fm10k_mbx_create_fake_disconnect_hdr(9)fm10k_mbx_create_error_msg(9)fm10k_mbx_validate_msg_hdr(9)fm10k_mbx_create_reply(9)fm10k_mbx_reset_work(9)fm10k_mbx_update_max_size(9)fm10k_mbx_connect_reset(9)fm10k_mbx_process_connect(9)fm10k_mbx_process_data(9)fm10k_mbx_process_disconnect(9)fm10k_mbx_process_error(9)fm10k_mbx_process(9)fm10k_mbx_disconnect(9)fm10k_mbx_connect(9)fm10k_mbx_validate_handlers(9)fm10k_mbx_register_handlers(9)fm10k_pfvf_mbx_init(9)fm10k_sm_mbx_create_data_hdr(9)fm10k_sm_mbx_create_connect_hdr(9)fm10k_sm_mbx_connect_reset(9)fm10k_sm_mbx_connect(9)fm10k_sm_mbx_disconnect(9)fm10k_sm_mbx_validate_fifo_hdr(9)fm10k_sm_mbx_process_error(9)fm10k_sm_mbx_create_error_msg(9)fm10k_sm_mbx_receive(9)fm10k_sm_mbx_transmit(9)fm10k_sm_mbx_create_reply(9)fm10k_sm_mbx_process_reset(9)fm10k_sm_mbx_process_version_1(9)fm10k_sm_mbx_process(9)fm10k_sm_mbx_init(9)
and that's the whole page, bestie π go copy some FIFO data, you absolute icon π
sign-off szn π«Ά this was ./drivers/net/ethernet/intel/f..., dated October 2026, and it's still fm10k_mbx_write_copy(9) β slay β¨π
π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms