ad_marker_response_received(9)
ad_marker_response_received(9) π
okay so this page is from the Kernel API Manual, and todayβs main character is ad_marker_response_received(9). kernel networking bestie, we are so in it π«Ά
NAME π
ad_marker_response_received β handle receive of a marker response frame. thatβs the whole assignment, bestie π
SYNOPSIS πΈ
void ad_marker_response_received (struct bond_marker *marker , struct
port *port );
the vibe check: it returns void, and it takes a struct bond_marker *marker plus a struct port *port. yes the spacing is exactly what the page says, donβt come for me π
ARGUMENTS π
markerβ marker PDU received. thatβs the PDU that arrived, bestie πportβ the port we're looking at. the one under our little microscope π
DESCRIPTION π¦
okay so hereβs the tea: this function does nothing. not a single thing. zero. zilch. π
Why? because we decided not to implement send and handle response for marker PDU's, in this stage, but only to respond to marker information. so it is intentionally empty at this point, and that is the whole lore. periodt π
SEE ALSO π₯
okay bestie, if you want the full 3ad cinematic universe, start with the kernel file and then go absolutely feral on these cross-references. all the icons are here π
- Kernel file
./drivers/net/bonding/bond_3ad.c __get_bond_by_port(9)__get_first_agg(9)__agg_has_partner(9)__disable_distributing_port(9)__enable_collecting_port(9)__disable_port(9)__enable_port(9)__port_move_to_attached_state(9)__port_is_collecting_distributing(9)__get_agg_selection_mode(9)__check_agg_selection_timer(9)__get_link_speed(9)__get_duplex(9)__ad_timer_to_ticks(9)__choose_matched(9)__record_pdu(9)__record_default(9)__update_selected(9)__update_default_selected(9)__update_ntt(9)__agg_ports_are_ready(9)__set_agg_ports_ready(9)__get_agg_bandwidth(9)__get_active_agg(9)__update_lacpdu_from_port(9)ad_lacpdu_send(9)ad_marker_send(9)ad_mux_machine(9)ad_rx_machine(9)ad_churn_machine(9)ad_tx_machine(9)ad_periodic_machine(9)ad_port_selection_logic(9)ad_agg_selection_logic(9)ad_clear_agg(9)ad_initialize_agg(9)ad_initialize_port(9)ad_enable_collecting(9)ad_disable_distributing(9)ad_enable_collecting_distributing(9)ad_disable_collecting_distributing(9)ad_marker_info_received(9)bond_3ad_initiate_agg_selection(9)bond_3ad_initialize(9)bond_3ad_bind_slave(9)bond_3ad_unbind_slave(9)bond_3ad_update_ad_actor_settings(9)bond_agg_timer_advance(9)bond_3ad_state_machine_handler(9)bond_3ad_rx_indication(9)ad_update_actor_keys(9)bond_3ad_adapter_speed_duplex_changed(9)bond_3ad_handle_link_change(9)bond_3ad_set_carrier(9)__bond_3ad_get_active_agg_info(9)bond_3ad_update_lacp_rate(9)bond_3ad_update_lacp_active(9)
mwah π this cutie comes from the ./drivers/net/bonding source tree, dated October 2026, and itβs filed under ad_marker_response_received(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