ixgbe_ptp_se...mestamp_mode(9)
π ixgbe_ptp_se...mestamp_mode(9) β like, the whole page, bestie π
okay so this is a page from the Kernel API Manual, and it's all about ixgbe_ptp_set_timestamp_mode, which lowkey is the function that sets your hardware up for whatever timestamp mode you asked for. yes bestie, PTP. hardware timestamps. we're doing this. π°οΈβ¨
β¨ NAME β¨
ixgbe_ptp_set_timestamp_mode β setup the hardware for the requested mode π
πΈ SYNOPSIS πΈ
int ixgbe_ptp_set_timestamp_mode (struct ixgbe_adapter *adapter , struct
kernel_hwtstamp_config *config );
like, it returns an int, takes two things, that's the whole vibe. π«Ά
π¦ ARGUMENTS π¦
adapterβ the private ixgbe adapter structure. your very own adapter. she's private, she's ixgbe, she's everything. πconfigβ the hwtstamp configuration requested. this is the ask. the dream. the configuration. β¨
π₯ DESCRIPTION π₯
okay so first up: outgoing time stamping can be enabled and disabled. play nice and disable it when it's requested, okay? even though like, it shouldn't cause any overhead when no packet actually needs it. no cap. and here's the rule that matters: at most one packet in the queue may be marked for time stamping. why?? because otherwise it'd be straight-up impossible to tell for sure which packet the hardware time stamp belongs to. π one packet. one stamp. don't be greedy.
Incoming time stamping is a whole different situation β it has to be configured via the hardware filters. and ngl, not all combinations are supported. in particular, the event type has to be specified. also matching the kind of event packet? not supported. the one exception, the icon, the main character: "all V2 events regardless of level 2 or 4". periodt. π
and here's a thing you need to know: since hardware always timestamps Path delay packets when timestamping V2 packets, regardless of the type specified in the register β only use V2 Event mode. seriously. this more accurately tells the user what the hardware is going to do anyways. it's giving honesty. it's giving transparency. slay π
β NOTE β
this may modify the hwtstamp configuration towards a more general mode, if required to support the specifically requested mode. π like bestie, she might generalize your config to make your specific ask work. that's the deal.
π SEE ALSO π
Kernel file ./drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c β the source, the origin, the mothership. π§
and now the whole friend group, in order, no skips, no cuts:
ixgbe_ptp_setup_sdp_X540(9),ixgbe_ptp_setup_sdp_X550(9),ixgbe_ptp_read_X550(9),ixgbe_ptp_read_82599(9),ixgbe_ptp_convert_to_hwtstamp(9),ixgbe_ptp_adjfine_82599(9),ixgbe_ptp_adjfine_X550(9),ixgbe_ptp_adjtime(9),ixgbe_ptp_gettimex(9),ixgbe_ptp_settime(9),ixgbe_ptp_feature_enable(9),ixgbe_ptp_check_pps_event(9),ixgbe_ptp_overflow_check(9),ixgbe_ptp_rx_hang(9),ixgbe_ptp_clear_tx_timestamp(9),ixgbe_ptp_tx_hang(9),ixgbe_ptp_tx_hwtstamp(9),ixgbe_ptp_tx_hwtstamp_work(9),ixgbe_ptp_rx_pktstamp(9),ixgbe_ptp_rx_rgtstamp(9),ixgbe_ptp_hwtstamp_get(9),ixgbe_ptp_hwtstamp_set(9),ixgbe_ptp_start_cyclecounter(9),ixgbe_ptp_init_systime(9),ixgbe_ptp_reset(9),ixgbe_ptp_create_clock(9),ixgbe_ptp_init(9),ixgbe_ptp_suspend(9),ixgbe_ptp_stop(9)
iykyk π
okay that's the page!! mwah π this one came from ./drivers/net/ethernet/intel/i... and it's dated October 2026, and yeah the title's still ixgbe_ptp_se...mestamp_mode(9) because that's her full government name. bye bestie, go timestamp something πβ¨π«Ά
π¦ 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