[dpdk-dev] [PATCH v3 00/16] remove mbuf timestamp

[David Marchand]

On Tue, Nov 3, 2020 at 1:14 AM Thomas Monjalon <thomas at 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.
>
> 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.

For the series:
Acked-by: David Marchand <david.marchand at redhat.com>


-- 
David Marchand