From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 18383427E7; Tue, 21 Mar 2023 02:00:53 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 944D440697; Tue, 21 Mar 2023 02:00:52 +0100 (CET) Received: from smtpbguseast1.qq.com (smtpbguseast1.qq.com [54.204.34.129]) by mails.dpdk.org (Postfix) with ESMTP id 00A4440693 for ; Tue, 21 Mar 2023 02:00:50 +0100 (CET) X-QQ-mid: bizesmtp63t1679360445tmip6vrh Received: from DESKTOPGF9TM7H ( [125.42.32.4]) by bizesmtp.qq.com (ESMTP) with id ; Tue, 21 Mar 2023 09:00:44 +0800 (CST) X-QQ-SSF: 00000000000000C0I000000A0000000 X-QQ-GoodBg: 0 From: To: "'Stephen Hemminger'" Cc: References: <1CCF1B14C9842CED+002501d95b20$272f1b60$758d5220$@netitest.com> <20230320095342.756879fb@hermes.local> In-Reply-To: <20230320095342.756879fb@hermes.local> Subject: =?UTF-8?Q?=E5=9B=9E=E5=A4=8D:_=E5=9B=9E=E5=A4=8D:_af=5Fpacket_can't_send?= =?UTF-8?Q?_packet_more_than_framecnt?= Date: Tue, 21 Mar 2023 09:00:45 +0800 Message-ID: <51FE0C642670EC4B+002901d95b90$91ed5a50$b5c80ef0$@netitest.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJ7S/WF+VpExSgouDpcVBFXPDSmcgJLE5Lsra4v1rA= Content-Language: zh-cn X-QQ-SENDSIZE: 520 Feedback-ID: bizesmtp:netitest.com:qybglogicsvr:qybglogicsvr5 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hi Stephen, Thanks for your response, my OS is CentOS7.9, so the kernel is 3.10. = However, the issue has been resolved depend on new DPDK code. Regards, Haifeng -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6----- =E5=8F=91=E4=BB=B6=E4=BA=BA: Stephen Hemminger = =20 =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2023=E5=B9=B43=E6=9C=8821=E6=97=A5 = 0:54 =E6=94=B6=E4=BB=B6=E4=BA=BA: hfli@netitest.com =E6=8A=84=E9=80=81: dev@dpdk.org =E4=B8=BB=E9=A2=98: Re: =E5=9B=9E=E5=A4=8D: af_packet can't send packet = more than framecnt On Mon, 20 Mar 2023 19:36:02 +0800 wrote: > Hi, >=20 > The issue has been resolved when I patched new code from dpdk 22.12,=20 > my dpdk 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 = 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.