[dpdk-dev] [PATCH v2 00/14] remove mbuf timestamp
Thomas Monjalon
thomas at monjalon.net
Sun Nov 1 19:08:40 CET 2020
01/11/2020 19:06, Thomas Monjalon:
> 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.
>
> As a consequence, 8 bytes can be re-allocated to dynamic fields
> in the first half of mbuf structure.
> It is still open to change more the mbuf layout.
>
> This mbuf layout change is important to allow adding more features
> (consuming more dynamic fields) during the next year,
> and can allow performance improvements with new usages in the first half.
The changelog was missing:
v2:
- remove optimization to register only once in ethdev
- fix error message in latencystats
- convert rxtx_callbacks macro to inline function
- increase dynamic fields space
- do not move pool field
More information about the dev
mailing list