Propagate DPDK mbuf RX timestamp to FreeBSD mbuf rcv_tstmp#1051
Merged
jfb8856606 merged 2 commits intoF-Stack:devfrom Mar 20, 2026
Merged
Propagate DPDK mbuf RX timestamp to FreeBSD mbuf rcv_tstmp#1051jfb8856606 merged 2 commits intoF-Stack:devfrom
jfb8856606 merged 2 commits intoF-Stack:devfrom
Conversation
Enable RTE_ETH_RX_OFFLOAD_TIMESTAMP on ports where the NIC supports it, register the timestamp dynamic field and flag via rte_mbuf_dyn_rx_timestamp_register() after rte_eth_dev_start() (when the PMD has registered the dynfield), and copy it into the FreeBSD mbuf's m_pkthdr.rcv_tstmp so that the existing SO_TIMESTAMP / SCM_TIMESTAMP path delivers it to userspace. Uses the DPDK 23.11 dynamic field API: checks the registered dynflag mask per-packet (not the legacy RTE_MBUF_F_RX_IEEE1588_TMST) and reads the timestamp via RTE_MBUF_DYNFIELD at the registered offset. When HW timestamps are not available the offload is not enabled, the dynflag is never set, and the new code path is never entered — fully backward compatible. Fixes: F-Stack#1045
Add LINUX_SO_TIMESTAMP (29) to the socket option translation table so that applications using the Linux syscall wrapper can enable packet receive timestamps via setsockopt(fd, SOL_SOCKET, SO_TIMESTAMP, ...).
Contributor
|
Thanks for the PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
RTE_ETH_RX_OFFLOAD_TIMESTAMPon ports where the NIC supports itrte_mbuf_dyn_rx_timestamp_register()afterrte_eth_dev_start()(DPDK 23.11 dynamic field API)m_pkthdr.rcv_tstmpso that the existingSO_TIMESTAMP/SCM_TIMESTAMPpath delivers it to userspaceLINUX_SO_TIMESTAMP(29) to FreeBSDSO_TIMESTAMPinff_syscall_wrapper.cso applications using the Linux syscall wrapper can enable receive timestamps viasetsockopt()Uses the registered dynflag mask per-packet (not the legacy
RTE_MBUF_F_RX_IEEE1588_TMST) and reads the timestamp viaRTE_MBUF_DYNFIELDat the registered offset.When HW timestamps are not available the offload is not enabled, the dynflag is never set, and the new code path is never entered — fully backward compatible.
Fixes: #1045