Re: [RFC 0/1] ethdev: per-packet Tx timestamp slot management

On 20-08-2026 10:11 am, Naga Harish K, S V wrote:

rte_mbuf structure has "timesync" field, which can be used for the slot.
 This way mbuf dynamic field use can be avoided.

"timesync" in rte_mbuf is already an established RX-side metadata field 
and not a generic TX slot carrier. As it is used as RX-side timestamp 
metadata, not as a generic TX slot ID. If the same field suddenly meant 
“TX slot handle” for one PMD and “RX queue/timestamp tag” for another, 
the ABI would become ambiguous and driver-specific, while the 
dynamic-field approach keeps the per-packet slot metadata explicit and 
portable. For that reason, we prefer the dynamic-field design for this 
feature.