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 9ACC2A0544 for ; Fri, 23 Sep 2022 08:36:25 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 91A40400D7; Fri, 23 Sep 2022 08:36:25 +0200 (CEST) Received: from NAM02-DM3-obe.outbound.protection.outlook.com (mail-dm3nam02on2088.outbound.protection.outlook.com [40.107.95.88]) by mails.dpdk.org (Postfix) with ESMTP id 7DC2F4003C for ; Fri, 23 Sep 2022 08:36:23 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hBJNLAB3mC4r4tJdjXv3x20WmN7SSWEZZLJ2zDaoVtLJurskPcLErZkRj9trznNDn9VeUXsOO5OulwWHm0Ykkv8rwmW7IqbMoiI/hhldoRfhS7iocQGFDajFSWeOj7iP/Mq8sNg98awo+C5BO1pGu1uhonnlav7b9BXiaTXyPGYrgApyZkLYm9Rr6pbzT6qH/Ke4rX6C3Rflz8mzL9/5LjyCu0aoHxSnXO8nru+fx+S/64yI/QHlgug/vm/t28ljVOx+Eod11qXAT+BPhD2wg8/OPF7M2UUBGbkL8wKte88kWmSWczBJW/LyS3+GPM29vDRbu5qIaxX5Ur7mofoTmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=q/5UyZcESixN+DjEI8k8Y4UnpxVg+G07FIrpuNAs/Dw=; b=LbOUpSIZqgvfuvyvAnx8I7Zxuigbb+pb1u9gpnOwhYVoQxPpmQN5yd2cvHR7t4PQLh79KzTtzQYEQzOMGkmMP/Axort62MIFdMlEnOd4MSfZSldkwAQr6gLV/o3XLHrMxH8XeKCwNnkQqYU4R6s87FsNZiJsK3pcjT2O8FqGYdfXmwgOnr3RGomTz/Kra1FiWTEAiDkblwZg+UFDXl5j8VlYTvoYbroVtvTENeuPSSP2lgz6REB3Yqt2cBQlyOQbLWij3Yl/rHBxRQAuNdLL2aA8HpWfnWwEzPLehc4FiLlh4vmEvupOr6fPb5u0uGEDrJpKksBi7gyFAZYmVxIrGA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass header.d=amd.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amd.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=q/5UyZcESixN+DjEI8k8Y4UnpxVg+G07FIrpuNAs/Dw=; b=mcxX6yhDE0oxS6Y9jeL6INMTK981Ardz1uJ8MElLBLzBGtp7WBWra0ekFAFSfTIbA9joTTlahG56SV8+I1dzXu0Nt5TqGaopdKJwzpjwcjwHIeNUNMpPfqSQsH3xQuqblF5ERFRK+cynFmN5jx02J3cyr9vWlK93RHUvgmBXnmw= Received: from MN2PR12MB3085.namprd12.prod.outlook.com (2603:10b6:208:c5::29) by MN0PR12MB5954.namprd12.prod.outlook.com (2603:10b6:208:37d::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5654.14; Fri, 23 Sep 2022 06:36:21 +0000 Received: from MN2PR12MB3085.namprd12.prod.outlook.com ([fe80::c918:5d6f:11dc:d7bc]) by MN2PR12MB3085.namprd12.prod.outlook.com ([fe80::c918:5d6f:11dc:d7bc%5]) with mapi id 15.20.5654.020; Fri, 23 Sep 2022 06:36:18 +0000 From: "Varghese, Vipin" To: "users@dpdk.org" Subject: Re: Issue on capturing using DPDK Pdump on secondary interface Thread-Topic: Issue on capturing using DPDK Pdump on secondary interface Thread-Index: AQHYzxbJz4EKTjkhZEK0Ya8FbLKfQA== Date: Fri, 23 Sep 2022 06:36:18 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-IN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_Enabled=true; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_SetDate=2022-09-23T06:36:14Z; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_Method=Standard; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_Name=General; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_SiteId=3dd8961f-e488-4e60-8e11-a82d994e183d; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_ActionId=777d5ccd-d989-4e38-a880-8875dde14460; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_ContentBits=1 msip_label_4342314e-0df4-4b58-84bf-38bed6170a0f_enabled: true msip_label_4342314e-0df4-4b58-84bf-38bed6170a0f_setdate: 2022-09-23T06:36:14Z msip_label_4342314e-0df4-4b58-84bf-38bed6170a0f_method: Standard msip_label_4342314e-0df4-4b58-84bf-38bed6170a0f_name: General msip_label_4342314e-0df4-4b58-84bf-38bed6170a0f_siteid: 3dd8961f-e488-4e60-8e11-a82d994e183d msip_label_4342314e-0df4-4b58-84bf-38bed6170a0f_actionid: e0f9f60c-0e28-46f6-ae1b-e73a3c44b5bf msip_label_4342314e-0df4-4b58-84bf-38bed6170a0f_contentbits: 0 authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=amd.com; x-ms-publictraffictype: Email x-ms-traffictypediagnostic: MN2PR12MB3085:EE_|MN0PR12MB5954:EE_ x-ms-office365-filtering-correlation-id: 35df6870-6267-4c3a-0202-08da9d2dec21 x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: NrfDQ7in3lP7lCRId9oJzVXXLhi6UQGr2C5Sr67ow8YvYr7YMTVvO9ntlqunO881Jo94jTcgQm25lq44uKfejrNJWOpm6U3SEfL+CgYRLfCoziLL+t44M2iZ/xAiJfgKcVjqivIdoV7eCDrFeuPsdgMPs2IeiTy//8z5oDCANQiw4Du2uSCcuRv2CV506ChFuvKyzLxu3wM+d7Lax4jDqNcmB1dBEeW0V9FNddaAKeTayXmRqVxIIzwqa+HOmxFQ3RfdUYwQHjX1/mUkn78I8PbNaYG9mMugJZaj1m1TyP+Q2PFQl/US02bo0SpscAkHJ2PXC7EFReJu6nmKA1tm36D24NOu4ybbrqv+O5tdKVGVSYnQadpIWSQmL3NiQoD3rTyWBB4kVnjZyw/eTCpJaz374yCzsj2Paui2/IVmf6Ni629KqWqq/TEf5nKYMagOKqTBUhk913GPANxnRcIOpfdVnayVXShIVt6ax228cXVJknkHFffVUt/dDo6FlvqtQqPbhe7KnB9AkL6MgC7OVJRNa3xy1rGKJwcn1YO15P1w2LG7ExRAXX2psinhpw5j42vL1OKanmeubFXcErHHY2r18ReVSfbacZjWGLteD/jloy9ybOSFIbl/4Dsc/6LSg1Q9Fzh3RFgSS8YnBEpRPNC4TeT/+tXTa8VDZkrEuxdHRYcChJZ76JfZwBusgJr9Q1f3EiDgTpAJLyUzu9xQK6G6gpxQSci0fITk9klRz4rdNR0OMxa5AC+/EAqeY2aqS2MsDvGwS15lxmS37TOidep9qJonh78Ar6Y/vqALRJA= x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR12MB3085.namprd12.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230022)(4636009)(346002)(366004)(396003)(39860400002)(136003)(376002)(451199015)(478600001)(53546011)(26005)(71200400001)(55016003)(45080400002)(8936002)(5660300002)(9686003)(6506007)(7696005)(6916009)(186003)(41300700001)(38070700005)(33656002)(76116006)(66946007)(52536014)(38100700002)(2906002)(66446008)(64756008)(66476007)(83380400001)(86362001)(66556008)(316002)(966005)(122000001)(8676002)(30864003); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?DZf6ZsP4UiZPX4CdTN0Pdrj6h8whz4nOnTfUfY21AgN+3P/dg/nK/59NhY9q?= =?us-ascii?Q?Q0GQtI623Idj8ILRGzRbw3chMDqswUu7ECCUw8V5FJb3eTkJ1dvFmB62rhLT?= =?us-ascii?Q?GL+LYG23+e5nVSp1g3DbFCRN8Zm/5DaPkZa5SMy6rtB6/yuVNU9V4b+6B9HT?= =?us-ascii?Q?0g/chtATaZTItoPogmVGY0nJOVqrab5PNvCYN7zT4dTH16YEJb9jV6xv0FrB?= =?us-ascii?Q?DH8ZjD0L09I1BGRf1+7de+Ss08aZbGjDUDoSxVo8PimOIlG7lr4WEd0wNwOF?= =?us-ascii?Q?YQ9VAJASFs0K0V5TVz1zakFLLYaefxlucMQ4n27McnFaNg1K4NsyZqTGJdy0?= =?us-ascii?Q?IFe8qyTNTIUSYGMlXsuw1QFFa5PJMAGoMbPzKX7STL1beofWunV+mCYRTxUO?= =?us-ascii?Q?pxLjt88TKxyg6aDVzXt6gU0Xr1I1y6W+cSlsRc6dfNnrpAzjNZaVoRGQHPQC?= =?us-ascii?Q?jdI9ROLaBSYsmxWX7BuinQKxRYrlNEorBhrNGDPdwiWlFk50F/rpuk1O9wu/?= =?us-ascii?Q?jTAXOBxoWAV1PCWEgb3m+nlrxsUZjqKS/0RLj2LO902xE47Haoosd4C3A4eb?= =?us-ascii?Q?FYe8dmvOkxhBBDCHD2zZWYt3zezj3QjN6g8+KJLCgm6z0SyhOYmGoYSi43/n?= =?us-ascii?Q?ygIxu4YDHKBORkBJmebD/N5YVLWNxUKMxlHtmOSga5bCKHVw5cy7M03G54is?= =?us-ascii?Q?U+/PPakLDD/kQweL8lxmyxcpMi1Kb28FE6dYx2jCL7Xv4GMXk4QQPQw6VmWN?= =?us-ascii?Q?/XXApzOGxTZonu1tBToicU27fl4ClMwz+p37GsBW9/1f7ET4q6bKMJZio57q?= =?us-ascii?Q?Ul9qoO/hI1CuShDodRpDTMZ0Iz/DGVMNSVnqWsBrD7SIP9hqrlHc4xA7tJIk?= =?us-ascii?Q?oTJ8q5fp9iGj5raOLHP10Lnds4jD0wTWqqDOvip8ysoufVfajq/zQySrO/y4?= =?us-ascii?Q?y5/TiJ4SkOqHCv2NbOmJYsvMRDlnNgbgKGFUWcB3LHaqg42n8QfSyHiVMqLW?= =?us-ascii?Q?47aXJQBqhaERKtlkQjLukgiJGZtYPtGLus5oaxXDo0JwQvKZHiheD6iqDDoV?= =?us-ascii?Q?E4My8eqg/bU/n5SKBiLUjPXlFTD3vLQdGAnujgovksqbcjlLkFsX7sTf+rlC?= =?us-ascii?Q?eogr0c9p3TVIx6L5du9DbMB0ywhnE/4zlFfH2R9erbjbGuYM0jSWPiFUdetj?= =?us-ascii?Q?G0Lp5mEfuj5XTKYIcqvCCR/yzPOKitlKh/HBl+aRwuCwHtwgjMrPr7DABbu4?= =?us-ascii?Q?CPGTLJpq+Ty+ZLZOhyW63xXcqd7A5Zq8/1oMdc4HvrNAnE40FPU+mqeQ45v9?= =?us-ascii?Q?rCghNdgEVh44iIG2VI/ipP9dft5QVArw7EfjgMcMjr+hLU93TIOU5eY4O1x8?= =?us-ascii?Q?2iEyL9RqqY/xaJ0WM2rRhAsxk0BbulDSjfTBjlxcitqAGKLiKQXaPjq2vOQZ?= =?us-ascii?Q?VH0Qk/lg6vcr477YZNRf5xJ3K98R4BjfZcz48kHkXl9bSLJ9m5HjiebP9/4Q?= =?us-ascii?Q?hdl4XDOGmHNXa+z+fIOfAP/uYbtbnVTf9zLxJg6T5ohNRtzsKN05Rj4xX4+t?= =?us-ascii?Q?cTRoeXdLw4RroVHNUGU=3D?= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: MN2PR12MB3085.namprd12.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 35df6870-6267-4c3a-0202-08da9d2dec21 X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Sep 2022 06:36:18.6553 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 3dd8961f-e488-4e60-8e11-a82d994e183d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: KQ1fO5fxOUk8hY6hv9AGRXbqBHOlmBZdGm9BiXo0e88GsMdNHJeAd1dMvzD3dVi+63S69cm9N9YXg2IbEdjxpw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN0PR12MB5954 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 [AMD Official Use Only - General] Hi Srinivas, Based on the internal testing with dpdk-pdump I do not find the issue with = PDUMP capture with secondary interface.=20 I am able capture for both port0 and port1. Following are the steps I follo= wed ``` cd [dpdk parent folder] cd app/pdump gcc main.c $(pkg-config --static --libs --cflags libdpdk) -o mypdump in terminal 1: start dpdk testpmd "dpdk-testpmd -l 15-16 --vdev=3Dnet_tap0= --vdev=3Dnet_tap1 --no-pci -- -i --forward=3Dtxonly". Then execute "start"= in interactive terminal in terminal 2: start pdump application "./mypdump --no-pci -l 12 -- --pdum= p 'port=3D0,queue=3D*,tx-dev=3D/tmp/0.pcap'" in terminal 3: start pdump application "./mypdump --no-pci -l 13 -- --pdum= p 'port=3D1,queue=3D*,tx-dev=3D/tmp/1.pcap'" ``` Stop pdump captures in terminal 2 and 3 Execute on terminal ` tcpdump -nr /tmp/0.pcap` Execute on terminal ` tcpdump -nr /tmp/1.pcap` ``` # tcpdump -nr /tmp/1.pcap | more reading from file /tmp/1.pcap, link-type EN10MB (Ethernet) 23:25:15.682623 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22 23:25:15.682625 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22 ``` Hence DPDK PDUMP works with second port. I have also tried the same with In= tel X710 nic too. note:=20 1. are you building DPDK application in shared library mode? If yes please = ensure for application and dpdk-pdump pass all relevant shared library to i= nit 2. are you passing desired pcie device? Please use dpdk option `-a` to pass= the interfaces used in primary application for secondary=20 3. have you installed pcap-dev library? DPDK pdump makes use of pcap-dev li= b to write as pcap file. Hence the target should have the library. 4. does the DPDK logs gives any hint? Please re-run both primary and pdump = with eal option `--log-level=3D8` Regards Vipin Varghese=20 > -----Original Message----- > From: users-request@dpdk.org > Sent: Saturday, September 17, 2022 3:30 PM > To: users@dpdk.org > Subject: users Digest, Vol 356, Issue 9 >=20 > Caution: This message originated from an External Source. Use proper > caution when opening attachments, clicking links, or responding. >=20 >=20 > Send users mailing list submissions to > users@dpdk.org >=20 > To subscribe or unsubscribe via the World Wide Web, visit >=20 > https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fmail > s.dpdk.org%2Flistinfo%2Fusers&data=3D05%7C01%7Cvipin.varghese%40a > md.com%7C905f5dbf0db045e968b408da989364df%7C3dd8961fe4884e608e1 > 1a82d994e183d%7C0%7C0%7C637990056071355174%7CUnknown%7CTWFpb > GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI > 6Mn0%3D%7C3000%7C%7C%7C&sdata=3Dl0csfydT0085Uztryx%2Bj1mGOy > 2DS5DIkCfnbMgkOIx8%3D&reserved=3D0 > or, via email, send a message with subject or body 'help' to > users-request@dpdk.org >=20 > You can reach the person managing the list at > users-owner@dpdk.org >=20 > When replying, please edit your Subject line so it is more specific than = "Re: > Contents of users digest..." >=20 >=20 > Today's Topics: >=20 > 1. Re: l2fwd: Requested device 0000:02:00.0 cannot be used > (Ubuntu 22.04, DPDK 22.07, N5095, I225-V) (Stephen Hemminger) > 2. Re: Issue on capturing using DPDK Pdump on secondary > interface. (Stephen Hemminger) >=20 >=20 > ---------------------------------------------------------------------- >=20 > Message: 1 > Date: Fri, 16 Sep 2022 08:10:59 -0700 > From: Stephen Hemminger > To: F32 > Cc: users@dpdk.org > Subject: Re: l2fwd: Requested device 0000:02:00.0 cannot be used > (Ubuntu 22.04, DPDK 22.07, N5095, I225-V) > Message-ID: <20220916081059.5b9841a1@hermes.local> > Content-Type: text/plain; charset=3DUS-ASCII >=20 > On Wed, 14 Sep 2022 11:18:11 +0800 (CST) > F32 wrote: >=20 > > Hi, > > > > > > Recently I'm testing dpdk on a mini PC with N5095 CPU and 5 I225-V > ethernet adapters under Ubuntu Server 22.04.1. > > > > > > $ uname -r > > 5.15.0-47-generic > > > > > > $ cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT > > GRUB_CMDLINE_LINUX_DEFAULT=3D"default_hugepagesz=3D1G > hugepagesz=3D1G hugepages=3D16 intel_iommu=3Don iommu=3Dpt" > > $ update-grub > > $ reboot > > > > > > $ dmesg | grep DMAR > > [ 0.016399] ACPI: DMAR 0x00000000787D6000 000088 (v02 INTEL EDK2 > 00000002 01000013) > > [ 0.016443] ACPI: Reserving DMAR table memory at [mem 0x787d6000- > 0x787d6087] > > [ 0.029273] DMAR: IOMMU enabled > > [ 0.093267] DMAR: Host address width 39 > > [ 0.093269] DMAR: DRHD base: 0x000000fed90000 flags: 0x0 > > [ 0.093276] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap > 1c0000c40660462 ecap 49e2ff0505e > > [ 0.093281] DMAR: DRHD base: 0x000000fed91000 flags: 0x1 > > [ 0.093287] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap > d2008c40660462 ecap f050da > > [ 0.093291] DMAR: RMRR base: 0x0000007b800000 end: 0x0000007fbfffff > > [ 0.093296] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 > > [ 0.093299] DMAR-IR: HPET id 0 under DRHD base 0xfed91000 > > [ 0.093301] DMAR-IR: Queued invalidation will be enabled to support > x2apic and Intr-remapping. > > [ 0.095158] DMAR-IR: Enabled IRQ remapping in x2apic mode > > [ 0.288306] pci 0000:00:02.0: DMAR: Skip IOMMU disabling for graphic= s > > [ 0.372113] DMAR: No ATSR found > > [ 0.372115] DMAR: No SATC found > > [ 0.372118] DMAR: IOMMU feature fl1gp_support inconsistent > > [ 0.372120] DMAR: IOMMU feature pgsel_inv inconsistent > > [ 0.372122] DMAR: IOMMU feature nwfs inconsistent > > [ 0.372124] DMAR: IOMMU feature pds inconsistent > > [ 0.372125] DMAR: IOMMU feature eafs inconsistent > > [ 0.372127] DMAR: IOMMU feature prs inconsistent > > [ 0.372129] DMAR: IOMMU feature nest inconsistent > > [ 0.372130] DMAR: IOMMU feature mts inconsistent > > [ 0.372132] DMAR: IOMMU feature sc_support inconsistent > > [ 0.372134] DMAR: IOMMU feature dev_iotlb_support inconsistent > > [ 0.372136] DMAR: dmar0: Using Queued invalidation > > [ 0.372141] DMAR: dmar1: Using Queued invalidation > > [ 0.373075] DMAR: Intel(R) Virtualization Technology for Directed I/= O > > > > > > $ lspci > > lspci > > 00:00.0 Host bridge: Intel Corporation Device 4e24 > > 00:02.0 VGA compatible controller: Intel Corporation JasperLake [UHD > > Graphics] (rev 01) > > 00:04.0 Signal processing controller: Intel Corporation Dynamic Tuning > > service > > 00:08.0 System peripheral: Intel Corporation Device 4e11 > > 00:14.0 USB controller: Intel Corporation Device 4ded (rev 01) > > 00:14.2 RAM memory: Intel Corporation Device 4def (rev 01) > > 00:15.0 Serial bus controller: Intel Corporation Serial IO I2C Host > > Controller (rev 01) > > 00:15.2 Serial bus controller: Intel Corporation Device 4dea (rev 01) > > 00:16.0 Communication controller: Intel Corporation Management Engine > > Interface (rev 01) > > 00:17.0 SATA controller: Intel Corporation Device 4dd3 (rev 01) > > 00:19.0 Serial bus controller: Intel Corporation Device 4dc5 (rev 01) > > 00:19.1 Serial bus controller: Intel Corporation Device 4dc6 (rev 01) > > 00:1c.0 PCI bridge: Intel Corporation Device 4db8 (rev 01) > > 00:1c.4 PCI bridge: Intel Corporation Device 4dbc (rev 01) > > 00:1c.5 PCI bridge: Intel Corporation Device 4dbd (rev 01) > > 00:1c.6 PCI bridge: Intel Corporation Device 4dbe (rev 01) > > 00:1c.7 PCI bridge: Intel Corporation Device 4dbf (rev 01) > > 00:1e.0 Communication controller: Intel Corporation Device 4da8 (rev > > 01) > > 00:1e.3 Serial bus controller: Intel Corporation Device 4dab (rev 01) > > 00:1f.0 ISA bridge: Intel Corporation Device 4d87 (rev 01) > > 00:1f.3 Audio device: Intel Corporation Device 4dc8 (rev 01) > > 00:1f.4 SMBus: Intel Corporation JaserLake SMBus (rev 01) > > 00:1f.5 Serial bus controller: Intel Corporation JaserLake SPI (flash) > > Controller (rev 01) > > 01:00.0 Ethernet controller: Intel Corporation Ethernet Controller > > I225-V (rev 03) > > 02:00.0 Ethernet controller: Intel Corporation Ethernet Controller > > I225-V (rev 03) > > 03:00.0 Ethernet controller: Intel Corporation Ethernet Controller > > I225-V (rev 03) > > 04:00.0 Ethernet controller: Intel Corporation Ethernet Controller > > I225-V (rev 03) > > 05:00.0 Ethernet controller: Intel Corporation Ethernet Controller > > I225-V (rev 03) > > > > > > (after huge page setup) > > $ python3 dpdk-hugepages.py -s > > Node Pages Size Total > > 0 1607 2Mb 3Gb > > > > > > Hugepages mounted on /dev/hugepages /mnt/huge > > > > > > $ ifconfig enp2s0 down > > $ ifconfig enp3s0 down > > $ python3 dpdk-devbind.py --bind=3Dvfio-pci 0000:02:00.0 $ python3 > > dpdk-devbind.py --bind=3Dvfio-pci 0000:03:00.0 $ python3 dpdk-devbind.p= y > > -s > > > > > > Network devices using DPDK-compatible driver > > =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 > > 0000:02:00.0 'Ethernet Controller I225-V 15f3' drv=3Dvfio-pci unused=3D= igc > > 0000:03:00.0 'Ethernet Controller I225-V 15f3' drv=3Dvfio-pci unused=3D= igc > > > > > > Network devices using kernel driver > > =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 > > 0000:01:00.0 'Ethernet Controller I225-V 15f3' if=3Denp1s0 drv=3Digc > > unused=3Dvfio-pci *Active* > > 0000:04:00.0 'Ethernet Controller I225-V 15f3' if=3Denp4s0 drv=3Digc > > unused=3Dvfio-pci > > 0000:05:00.0 'Ethernet Controller I225-V 15f3' if=3Denp5s0 drv=3Digc > > unused=3Dvfio-pci > > > > > > No 'Baseband' devices detected > > =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 > > > > > > No 'Crypto' devices detected > > =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 > > > > > > No 'DMA' devices detected > > =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 > > > > > > No 'Eventdev' devices detected > > =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 > > > > > > No 'Mempool' devices detected > > =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 > > > > > > No 'Compress' devices detected > > =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 > > > > > > No 'Misc (rawdev)' devices detected > > =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 > > > > > > No 'Regex' devices detected > > =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 > > > > > > After the above configuration, dpck setup should be done. Then I tried = to > run l2fwd. It generates the following errror messages: > > > > > > $ ./l2fwd > > EAL: Detected CPU lcores: 4 > > EAL: Detected NUMA nodes: 1 > > EAL: Detected shared linkage of DPDK > > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > > EAL: Selected IOVA mode 'VA' > > EAL: VFIO support initialized > > EAL: Using IOMMU type 1 (Type 1) > > EAL: Probe PCI driver: net_igc (8086:15f3) device: 0000:02:00.0 > > (socket 0) > > EAL: Releasing PCI mapped resource for 0000:02:00.0 > > EAL: Calling pci_unmap_resource for 0000:02:00.0 at 0x1100800000 > > EAL: Calling pci_unmap_resource for 0000:02:00.0 at 0x1100900000 > > EAL: Requested device 0000:02:00.0 cannot be used > > EAL: Using IOMMU type 1 (Type 1) > > EAL: Probe PCI driver: net_igc (8086:15f3) device: 0000:03:00.0 > > (socket 0) > > EAL: Releasing PCI mapped resource for 0000:03:00.0 > > EAL: Calling pci_unmap_resource for 0000:03:00.0 at 0x1100904000 > > EAL: Calling pci_unmap_resource for 0000:03:00.0 at 0x1100a04000 > > EAL: Requested device 0000:03:00.0 cannot be used > > TELEMETRY: No legacy callbacks, legacy socket not created MAC updating > > enabled > > EAL: Error - exiting with code: 1 > > Cause: No Ethernet ports - bye > > > > > > It seems that the I225 adapters are not recognized by DPDK. I can not s= ee > any detailed reasons why the adapters cannot be used. > > Any suggestions to fix this issue? > > > > > > Regards, > > F32 >=20 > Check the IOMMU groups on that system. > Often multiple PCI devices (especially multi-port NICs) share a single IO= MMU > group and VFIO does not allow using these devices unless all subdevices i= n > the group are unbound from the kernel driver. >=20 >=20 > ------------------------------ >=20 > Message: 2 > Date: Fri, 16 Sep 2022 09:42:24 -0700 > From: Stephen Hemminger > To: Navin Srinivas > Cc: dev@dpdk.org, users > Subject: Re: Issue on capturing using DPDK Pdump on secondary > interface. > Message-ID: <20220916094224.4979921b@hermes.local> > Content-Type: text/plain; charset=3DUS-ASCII >=20 > On Thu, 25 Aug 2022 11:43:11 +0530 > Navin Srinivas wrote: >=20 > > Hello, > > > > We are facing a strange issue, we have the following setup for our > > application. We wanted to capture packets using dpdk pdump for our > > application, and started to notice an issue in capturing on DPDK 21.11 > > So we went back to DPDK 20.11 and we still saw the issue. > > > > [image: image.png] > > Think there is an issue in the pdump library to capture packets on the > > secondary interface. But I'm not sure where to look. > > APP1 - Primary APP > > APP2 - Secondary APP. > > Ports and ring inits are done by APP1 for APP2. > > > > We are able to capture packets using the standard example application > > of pdump and capture on port 0, but we are not able to capture on port1= . > > > > Has anyone come across this issue? Is there an open bug for this? > > The multi process is working properly, and we are able to transmit and > > receive packets on the secondary interface without any issue. We are > > facing issue only on capturing packets on that interface(port1). > > > > Are there any pointers where I can start to look? > > > > Thanks & Regards, > > Navin Srinivas >=20 > Pdump is a secondary application itself. >=20 > Pdump doesn't handle multiple interfaces well, it puts everything togethe= r. > You probably are better off using the new dumpcap which supports pcapng. > Pcapng supports multiple interfaces in single capture. >=20 >=20 > End of users Digest, Vol 356, Issue 9 > *************************************