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 EDAFF43E76 for ; Mon, 15 Apr 2024 09:11:18 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7001E402DE; Mon, 15 Apr 2024 09:11:18 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 5CC88402C9 for ; Mon, 15 Apr 2024 09:11:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1713165075; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vgdmc8Mi+K8gkEY3KoCnjMlvkoS1ywoIQQthi8MgP1A=; b=hrSx7Yv2FtxxSFoLhIHMq08E6kJ8ePX4zeH0qq3FWAhPgcJGdupJ7cNAyYAaRmG7C2sniA LjT8StnpAwOX23CB7CCvcIpBRLp7XqQyJlCNSrkrX+YfoodzQ19Q3fSaYOSRSkyoNbrD1s 9yjhe+Xxr4RgObPUEsgyWANWLBQ0NfA= Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-70-hNaYIOuHMECu8tW-n3a2bw-1; Mon, 15 Apr 2024 03:11:14 -0400 X-MC-Unique: hNaYIOuHMECu8tW-n3a2bw-1 Received: by mail-lj1-f197.google.com with SMTP id 38308e7fff4ca-2d880c1c295so30969431fa.2 for ; Mon, 15 Apr 2024 00:11:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713165072; x=1713769872; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=vgdmc8Mi+K8gkEY3KoCnjMlvkoS1ywoIQQthi8MgP1A=; b=YMp+mOhryX5rRJiDymsQhgDgQF2NliT84+ZOKEeGN8nONnCL9uCfAaWpBNlkbGPNnd kVW7oWKREnoCGN3wJ7cZ09Di+UVQDVVfHNSjB/uTDOWXj/QEKmR68VR47Mb+D07gWF/j xtNGZCIe6YFbJwRJBR8eb3qzj4kFz+RBbE4k29zzTsZQZmZ3DRaBu6w33hkENetUxt/7 EDz+o06HgKfoXF932JKAsijdAo6A6EbyKPUsBEZkzKMSzdE9R9OVJ7GNzUqKk768+2fs fEwQnYbRRFAFoCIKqUFtAVfARjfaH9P3MzQJ2dZtcHb+lbwqxKDyKLRqdpvrT7E9hVYz KNLw== X-Gm-Message-State: AOJu0YyiBIQmXG0TlCLO7SqCY7OQNLB8lbzUNdnXqeEMi7NUhRQbn3xC rABMSTrsJbGgfgRU8i3NrEbClzgBIHEdBipTUijSyEbGjLI3V8XDwbL2fHG+xVNgMXtVG0dVXbZ k7TQupc+b1TAPUB9cLTuhGGewl2/DDYFGh6Sz7LDFLaAbA6vdcrF8lPvsZ2P8gblBd9rWU9NaaR v+/t7BtVYxLCFpenKsaQ== X-Received: by 2002:a2e:9e93:0:b0:2d8:b8c8:1311 with SMTP id f19-20020a2e9e93000000b002d8b8c81311mr7187449ljk.4.1713165072717; Mon, 15 Apr 2024 00:11:12 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFcNYC4+6MyfNqdZCdDwQQ6OY8ZL/vqSdmTulzzsWWrpPnsT+Hcx2w3dtJz5pizqZjjFrWdBtyiltH5G6C17Jk= X-Received: by 2002:a2e:9e93:0:b0:2d8:b8c8:1311 with SMTP id f19-20020a2e9e93000000b002d8b8c81311mr7187431ljk.4.1713165072349; Mon, 15 Apr 2024 00:11:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Mon, 15 Apr 2024 09:11:00 +0200 Message-ID: Subject: Re: cannot trx when use testpmd To: hao wang Cc: users@dpdk.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Hello, On Fri, Apr 12, 2024 at 9:51=E2=80=AFAM hao wang w= rote: > > I have a pmd that I am upstreaming to DPDK and currently testing. When I = use testpmd to test my pmd, I found that my pmd could trx in DPDK 23.07, bu= t it cannot in DPDK 23.11. After comparing the atlantic pmd between DPDK 23= .07 and 23.11, I see nearly no changes. I see the testpmd difference betwee= n DPDK 23.07 and DPDK 23.11 and think these changes may not cause the probl= em. > > But when I use pktgen to test the pmd, it's ok. > > Any suggestions? Nothing comes to mind. The simpler is to do a bisect. --=20 David Marchand