STRUCT IDPF_PTP_DEV_TIMERS(9)
β¨ struct idpf_ptp_dev_timers β system time & device time values π
okay so bestie, quick vibe check: this is a page from the Kernel API Manual, and it's all about a little struct called idpf_ptp_dev_timers πβ¨ She's not complicated, she's not doing too much β she just holds two timestamps so the driver can talk about "when" in two different clocks at once. iconic behaviour honestly.
πΈ SYNOPSIS πΈ
struct idpf_ptp_dev_timers {
u64 sys_time_ns;
u64 dev_clk_time_ns;
};
like... that's the whole thing. two u64 fields and a dream π
π Members π
sys_time_nsβ the system time value, expressed in nanoseconds β±οΈ that's your host's idea of now.dev_clk_time_nsβ the device clock time value, also expressed in nanoseconds π¦ that's the NIC's idea of now. and yes, they get to disagree, that's literally the whole point of keeping both.
ngl the _ns suffix is doing so much heavy lifting here β nanoseconds, bestie, not nanosleep π
π₯ SEE ALSO π₯
- Kernel file
./drivers/net/ethernet/intel/idpf/idpf_ptp.h struct idpf_ptp_cmd(9)enum idpf_ptp_access(9)struct idpf_ptp_secondary_mbx(9)enum idpf_ptp_tx_tstamp_state(9)struct idpf_ptp_tx_tstamp_status(9)struct idpf_ptp_tx_tstamp(9)struct idpf_ptp_vport_tx_tstamp_caps(9)struct idpf_ptp(9)idpf_ptp_info_to_adapter(9)idpf_ptp_is_vport_tx_tstamp_ena(9)idpf_ptp_is_vport_rx_tstamp_ena(9)
that's the whole PTP friend group right there, fr fr β go read them too if you wanna understand the full lore π
mwah π sending you off with the deets: this one lives in ./drivers/net/ethernet/intel/idpf, the date on it is October 2026, and the man page source tag is struct idpf_ptp_dev_timers(9). slay, 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