From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 115D3427E3;
	Mon, 20 Mar 2023 17:53:47 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id E3859410D0;
	Mon, 20 Mar 2023 17:53:46 +0100 (CET)
Received: from mail-pl1-f179.google.com (mail-pl1-f179.google.com
 [209.85.214.179])
 by mails.dpdk.org (Postfix) with ESMTP id B2F2940A80
 for <dev@dpdk.org>; Mon, 20 Mar 2023 17:53:45 +0100 (CET)
Received: by mail-pl1-f179.google.com with SMTP id bc12so12508921plb.0
 for <dev@dpdk.org>; Mon, 20 Mar 2023 09:53:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=networkplumber-org.20210112.gappssmtp.com; s=20210112; t=1679331225;
 h=content-transfer-encoding:mime-version:references:in-reply-to
 :message-id:subject:cc:to:from:date:from:to:cc:subject:date
 :message-id:reply-to;
 bh=pLCJV36v3/h0XznZT3cp8ki6ZpPkBIl0skABuNiN0bA=;
 b=m15XfGhmag9PhkGQeIxQRnYw1s+WnJtPsLlwE5MqmsJPx6et1oG9Egb9UVlxiFESlO
 zs/9nTN06JwC/PzSbmhy11PiupDg/PkYlFA2y6HL/HdVM7RmPvDmRaM68J8sIhUZ7o0F
 kJnTiFvVJ9Rp6JSXfYm5gYxx8Ky2l/D2xqu1v0uIH682pOTKgrnZHMRkKKLle5IVih2b
 nhkOen8J80D9Jg/jhDC45ald5cExD5q6HAWEQRC1eZCKfUJi+PmIdQ3ZM2IDI+eejP/z
 dcZlM6EB4wJJ/Dn3khYtc466gMoOOzx9p5dbilJhEudJedNcWBmCMNEsUzZFvaX6DBlQ
 HU8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112; t=1679331225;
 h=content-transfer-encoding:mime-version:references:in-reply-to
 :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=pLCJV36v3/h0XznZT3cp8ki6ZpPkBIl0skABuNiN0bA=;
 b=myMUP5lYa5VskHB810JsSUmYT+JzFdg7soB9HQKfiDi8/a7+VxZNDDquwPl6EmMose
 NVLmcGAP7qXe4T9n+/2BN+5IYBVPyg3bN4FnfbEB0LeBkWzZpL1IwDXwdN5eVXjYXbvc
 Sn6xnHav0bEyzMMMTx95H2zF3Rp5llIYcoCuZMMOJ7m4Xbs6hzvBgWt9FJrr/xxTLq0T
 0xpz7PUln9HG1y8XtSCTCbZOlBOao7STBYg+ZOq/NolMfe2JTEM3e+xswyLT0/MDNdhL
 Y8i0luXuElIFBsO7FPrSEnJnMuOwoe7JIjLPnMcZGx/53/byAljhwxZHYDLgleCL/q3c
 4g7g==
X-Gm-Message-State: AO0yUKV8ncLtdDw2B384rv5bKqEIvpSbjBpVtCDdyokpTL5XPXbJCOsI
 UgnOY7r+fbtHzGSU8NbQPvPVEqessqZU/snBqM2dHQ==
X-Google-Smtp-Source: AK7set/0Ut4Fr5TKeRq9XxRqI+BeKawX+OF/VXjiP+6EOVZxdw8pLJ2YRDxlw5hPMxDVm1Tfh+oNlw==
X-Received: by 2002:a05:6a20:4b2f:b0:d9:9e33:7215 with SMTP id
 fp47-20020a056a204b2f00b000d99e337215mr4172614pzb.10.1679331224700; 
 Mon, 20 Mar 2023 09:53:44 -0700 (PDT)
Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218])
 by smtp.gmail.com with ESMTPSA id
 h24-20020a63df58000000b0050f85ef50d1sm1706426pgj.26.2023.03.20.09.53.44
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Mon, 20 Mar 2023 09:53:44 -0700 (PDT)
Date: Mon, 20 Mar 2023 09:53:42 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: <hfli@netitest.com>
Cc: <dev@dpdk.org>
Subject: Re: =?UTF-8?B?5Zue5aSNOg==?= af_packet can't send packet more than
 framecnt
Message-ID: <20230320095342.756879fb@hermes.local>
In-Reply-To: <1CCF1B14C9842CED+002501d95b20$272f1b60$758d5220$@netitest.com>
References: <1CCF1B14C9842CED+002501d95b20$272f1b60$758d5220$@netitest.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

On Mon, 20 Mar 2023 19:36:02 +0800
<hfli@netitest.com> wrote:

> Hi,
>=20
> The issue has been resolved when I patched new code from dpdk 22.12, my d=
pdk
> version is 19.11
>=20
> Index: rte_eth_af_packet.c
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> --- rte_eth_af_packet.c (=E7=89=88=E6=9C=AC 44115)
> +++ rte_eth_af_packet.c (=E7=89=88=E6=9C=AC 44128)
> @@ -169,6 +169,29 @@
>  }
> =20
>  /*
> + * 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 sock=
et,
> +        * 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.