On Tue, 3 Nov 2020 15:09:15 +0100 Thomas Monjalon <tho...@monjalon.net> wrote:
> The mbuf field timestamp was announced to be removed for three reasons: > - a dynamic field already exist, used for Tx only > - this field always used 8 bytes even if unneeded > - this field is in the first half (cacheline) of mbuf > > After this series, the dynamic field timestamp is used for both Rx and Tx > with separate dynamic flags to distinguish when the value is meaningful > without resetting the field during forwarding. There should be a place in documentation which describes all the dynamic fields and their meaning. For example, which drivers/features set the field and the exact meaning. Is the timestamp in HW units, UTC units, or TSC ticks?
