On Mon, 20 Mar 2023 19:36:02 +0800
<h...@netitest.com> wrote:
> Hi,
>
> The issue has been resolved when I patched new code from dpdk 22.12, my dpdk
> version is 19.11
>
> Index: rte_eth_af_packet.c
> ===================================================================
> --- rte_eth_af_packet.c (版本 44115)
> +++ rte_eth_af_packet.c (版本 44128)
> @@ -169,6 +169,29 @@
> }
>
> /*
> + * Check if there is an available frame in the ring
> + */
> +static inline int
> +tx_ring_status_available(uint32_t tp_status)
> +{
> + /*
> + * We eliminate the timestamp status from the packet status.
> + * This should only matter if timestamping is enabled on the socket,
> + * but there is a bug in the kernel which is fixed in newer
> releases.
> + *
> + * See the following kernel commit for reference:
> + * commit 171c3b151118a2fe0fc1e2a9d1b5a1570cfe82d2
> + * net: packetmmap: fix only tx timestamp on request
Thanks for investigating, what kernel are you using?
That bug was fixed in 5.13 kernel (in 2021-05-11) almost 2 years ago.
It looks like it was also fixed in the LTS stable kernels.
DPDK probably should not be modified to handle kernel bugs that are
ready fixed in the current kernel LTS versions.
