e1000e_hwtstamp_set(9)

๐Ÿ“ฆ version 7.3.1, in nixpkgs unstable

๐Ÿ’… e1000e_hwtstamp_set(9)

okay so bestie, welcome to the Kernel API Manual โœจ โ€” this is the page for e1000e_hwtstamp_set, and honestly? it's giving "small function, big responsibilities." let's get into it ๐Ÿซถ


โœจ NAME โœจ

e1000e_hwtstamp_set โ€” control hardware time stamping โฑ๏ธ๐Ÿ’–


๐ŸŒธ SYNOPSIS ๐ŸŒธ

int e1000e_hwtstamp_set (struct net_device *netdev , struct
       kernel_hwtstamp_config *config , struct netlink_ext_ack *extack );

like yeah that's the whole signature, no cap. three args, one int coming back atcha ๐Ÿ’ซ


๐ŸŽ€ ARGUMENTS ๐ŸŽ€

  • netdev โ€” the network interface device structure ๐Ÿฆ‹ (yes, the whole device, she's the main character here)
  • config โ€” the timestamp configuration ๐Ÿ‘‘ (this is the vibe check for what you actually want stamped)
  • extack โ€” the netlink extended ACK report ๐Ÿ’Œ (where the receipts go if something goes sideways)

๐Ÿ”ฅ DESCRIPTION ๐Ÿ”ฅ

okay so, outgoing time stamping: you can enable it and you can disable it. and listen โ€” play nice and disable it when requested, bestie ๐Ÿ™ even though it shouldn't cause any overhead when no packet actually needs it. like, it's polite. it costs nothing. be that girl.

at most one packet in the queue may be marked for time stamping โ€” and this is a hard limit, fr fr. why? because otherwise it would be impossible to tell for sure which packet the hardware time stamp belongs to ๐Ÿ˜ญ like imagine two packets both claiming the stamp, chaos, drama, absolutely not.

now for incoming time stamping โ€” that one has to be configured via the hardware filters ๐Ÿงš no shortcuts, the filters are the moment.

and here's the fine print: not all combinations are supported. in particular, event type has to be specified โ€” no event type, no service ๐Ÿ’…

matching the kind of event packet? yeah, that's not supported ๐Ÿ™ˆ with exactly one exception: "all V2 events regardless of level 2 or 4" โ€” that one slays, that one works ๐ŸŒˆโญ

ngl, read the constraints twice. "not all combinations are supported" is doing a lot of heavy lifting in that sentence ๐Ÿ’€

๐Ÿ”ฎ SEE ALSO ๐Ÿ”ฎ

like okay that's a lot of friends but they're all real and they're all in the list, no skips, we don't do that here ๐Ÿซถ


and that's the page!! mwah ๐Ÿ’‹ this gem ships from the Kernel API Manual, source file ./drivers/net/ethernet/intel/e..., dated October 2026 ๐Ÿ—“๏ธโœจ go forth and stamp responsibly, bestie ๐Ÿฆ‹๐Ÿ’–๐ŸŒธ

๐Ÿ“ฆ where this page comes from