From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 12A7AA0540 for ; Tue, 14 Jul 2020 04:44:01 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DB1551D5DD; Tue, 14 Jul 2020 04:44:00 +0200 (CEST) Received: from CNSHJSMIN03.NOKIA-SBELL.COM (unknown [116.246.26.71]) by dpdk.org (Postfix) with ESMTP id CA37F1D51C for ; Tue, 14 Jul 2020 04:43:58 +0200 (CEST) X-AuditID: ac189297-dc7ff7000001b940-8b-5f0d1bdb0ea9 Received: from CNSHPPEXCH1607.nsn-intra.net (Unknown_Domain [135.251.51.107]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by CNSHJSMIN03.NOKIA-SBELL.COM (Symantec Messaging Gateway) with SMTP id 23.2E.47424.BDB1D0F5; Tue, 14 Jul 2020 10:43:39 +0800 (HKT) Received: from CNSHPPEXCH1601.nsn-intra.net (135.251.51.101) by CNSHPPEXCH1607.nsn-intra.net (135.251.51.107) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1847.3; Tue, 14 Jul 2020 10:43:38 +0800 Received: from CNSHPPEXCH1601.nsn-intra.net ([135.251.51.101]) by CNSHPPEXCH1601.nsn-intra.net ([135.251.51.101]) with mapi id 15.01.1847.007; Tue, 14 Jul 2020 10:43:38 +0800 From: "Wu, Jianyue (NSB - CN/Hangzhou)" To: "xiaoyun.li@intel.com" , "users@dpdk.org" CC: "Harouat, Karim (Nokia - FR/Lannion)" , "Meunier, Julien (Nokia - FR/Paris-Saclay)" , "Cheng, Fei 2. (NSB - CN/Hangzhou)" , "Lu, Malak (NSB - CN/Hangzhou)" , "Li, Jiu (NSB - CN/Hangzhou)" , "Pan, Jianyong (NSB - CN/Hangzhou)" , "Hong, Christian (NSB - CN/Hangzhou)" , "Fei, Xiang (NSB - CN/Hangzhou)" , "Ning, Gang (NSB - CN/Hangzhou)" , "Ren, Longlong (NSB - CN/Hangzhou)" , "Ye, Hua (NSB - CN/Hangzhou)" Thread-Topic: [dpdk-users] [dpdk-18.05] Issue while configuring VLAN ID and priority in VF Thread-Index: AdZZgUWuuNOZui7YTcmQ2DkuVfDM9w== Date: Tue, 14 Jul 2020 02:43:38 +0000 Message-ID: <1174405832d547f4b348f61a1d1ffed6@nokia-sbell.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.251.51.115] MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgkeLIzCtJLcpLzFFi42Jp/22crXtbmjfeYOchFovmg+tZLCYeX8/o wOTxa8FSVo/Fe14yBTBFcdmkpOZklqUW6dslcGVsauljLWhNqfi5qJGpgfFFRBcjB4eEgInE kY2BXYycHEICh5gkVs2U6WLkArL/MkqsvXiPCcLZxChxZ+MEdpAqNgEXiak75rOCNIsIhEms /GsBUsMscItV4uXFDYwgNcIC4RL/Jm5lAbFFBGIk1vyfwg5h60lcO32CDcRmEVCV+PaqEayG V8BOov91F1gvo4CYxPdTa5hAbGYBcYlbT+aD2RICAhJL9pxnhrBFJV4+/scK8YCSRN8GqPJU iU3HprNDjBSUODnzCcsERuFZSCbNQlI2C0kZRFxHYsHuT2wQtrbEsoWvmWHsMwceMyGLL2Bk X8Uo7ewX7OEV7OvpZ2Cs5+fv7emoG+zk6uOj5+zvu4kRGElrJCZN38H4fNYHvUOMTByMhxgl OJiVRHh5uHjjhXhTEiurUovy44tKc1KLDzFKc7AoifMeqPkZJySQnliSmp2aWpBaBJNl4uCU amDyWH7glZlryD/fdBVF0+k5C05sk57Yc0t/HX/WrERTG/Ztu/TlzhlYX9lWqPVwpe6be4Ur 1ey7b0fbaGedWDNDV1F7WWIh7y2eoLRrAp7J4h9/FOl2XLb90sz76Q23dIHQ+7eVzxOylNav WbSmvM/DLlCqT0iIa2ZPi/vztG8y06XXrrr6kuXSwjmMRrX3RBKvJNrcPvHZ4c3T89Ff3S7/ uDel/4PK/gWbjOrO3c9ULOx6b5a3i8nPcMX9EOe3+idX/9CREVZ4r9i2l61P8fv0NWbXjvAG 3ux2Z1yku2pbKXfDFpf0TjeDsJoD39wKdte/7Jmm6v13A99K7h9fm2bNW3leT8PX3S2xs77I 9qkSS3FGoqEWc1FxIgDSBwDFEwMAAA== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] [dpdk-18.05] Issue while configuring VLAN ID and priority in VF X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi, xiaoyun, Could you help give a hand about this issue? Thanks indeed:) Background: Simplified traffic flow is like this: Sender XEON X552 eth1 vf 0 -> Receive= r XEON X552 eth1 vf 0. Our requirement is to configure DPDK to support one VLAN ID, and with multi= ple priorities 0~7. Current configuration is: PVID: rte_eth_dev_set_vlan_pvid(port_id, 201, 1); VLAN offload: vlan_offload =3D rte_eth_dev_get_vlan_offload(port_id); vlan_offload &=3D ~ETH_VLAN_STRIP_OFFLOAD; vlan_offload &=3D ~ETH_VLAN_FILTER_OFFLOAD; vlan_offload &=3D ~ETH_VLAN_EXTEND_OFFLOAD; if (0 !=3D rte_eth_dev_set_vlan_offload(port_id, vlan_offload)) Spoof off, trust on: vf 0 MAC 02:40:43:80:01:39, spoof checking off, link-state auto, = trust on, query_rss off Test scenarios: =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 First scenario: set vlan in vf 0 -- priority always 0 =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 ip link show eth1 3: eth1: mtu 9194 qdisc mq state UP mode = DEFAULT group default qlen 1000 link/ether 02:40:43:80:01:38 brd ff:ff:ff:ff:ff:ff vf 0 MAC 02:40:43:80:01:39, vlan 201, spoof checking off, link-state auto, = trust on, query_rss off If we configure vlan in vf 0, then we can only send out packets with priori= ty 0. Even we already enabled mbuf->ol_flags |=3D PKT_TX_VLAN_PKT; and set correc= t mbuf->vlan_tci. =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 Second scenario: not set vlan in vf 0 -- can't recv =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 3: eth1: mtu 9194 qdisc mq state UP mode = DEFAULT group default qlen 1000 link/ether 02:40:43:80:01:38 brd ff:ff:ff:ff:ff:ff vf 0 MAC 02:40:43:80:01:39, spoof checking off, link-state auto, trust on, = query_rss off If we don't set vlan in vf 0, then we can send out in sender XEON X552 eth1= vf 0 with correct VLAN ID and priority, >From tcpdump in mirrored traffic of receiver XEON, we can see the packet ha= s correct VLAN ID and priority, but the problem is packet silently dropped. From DPDK counters, we can't se= e the packet received in receiver XEON X552 eth1 vf0. When we enable promiscuous mode, we can see th= e packets arrive in receiver XEON, and VLAN ID, priority is correct. but can't arrive at DPDK. >From my simple assumption, maybe we need second scenario, to support multip= le priorities. But how to configure to let the packet pass vf 0? Did I miss something in my configuration? Thanks indeed in advance! Best Regards, Dave(Jianyue)