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 7AF66A04AB; Thu, 7 Nov 2019 07:01:30 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CED431E8AB; Thu, 7 Nov 2019 07:01:29 +0100 (CET) Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70078.outbound.protection.outlook.com [40.107.7.78]) by dpdk.org (Postfix) with ESMTP id D83C91E8A4 for ; Thu, 7 Nov 2019 07:01:27 +0100 (CET) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AWJ/5+r84/Aa6hEV2DwR2FMIZXTCk5FuPo8P/76tzQWyk2FyqMCE1gzkTJgHiwC7Y6W/anqq+s+vXJEG6B1biDP9QbnM4EHK0ImYgZsKmxXM7Tkw5su7MwB3fRM+Yx5WaxXx9Q3O6hJM7t84perXm2Floof9GtiO507kVMMHSQBtPVWq/JiVL44uGn5t/a242ut3UIaQqntLyA7xhfk5kEQGqGm0ZoAnA4TuL1FSG9B3Y6Pq6kk2ArRDkMBunxLv3+qJzNYSrZ09mYluiaPdWfca6yWJhBOolHNp7cQY2+VxcC0v3H8vbqt29Ds6MwrY3+6gfHYC/LtAdAbCqc+VDg== 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-SenderADCheck; bh=Xpw/WQnIGRFxAYGFrcFkI0AxAiZXdiK4VDngXSAfFnI=; b=BYaOTWf9/gGXiZQxlpG/9MIs6fC4atpl5DXlonXY/SGnFb2Lz9hCQsLadFIq6OmtFqN8t7ObrWhjeLqcnhQQ+YWv2WI7Jj+CH1BsrSIloB8H3IYez03WlA/Nh7xXQH7eOAhEMjlWndcxgfN39kd5wNPBfl5/wkfX3NHfmxssr52MwNHi0+vkFiLkm1rpCX5wLgG0rjtA7TM+Q4uDxPy6z9+aT8IKfGGNEgXnRDPiGysYH6Owp6rFZFr8qITKsGP06LbilLx0p1Fag2J+bq4KjB+yNNSlDQ/pCWsat9pdOLaAtzsOk594wAm+ZTlxFy+B0p4+LDHYLbL7AJC0sqfvsQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=mellanox.com; dmarc=pass action=none header.from=mellanox.com; dkim=pass header.d=mellanox.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Xpw/WQnIGRFxAYGFrcFkI0AxAiZXdiK4VDngXSAfFnI=; b=cUh5WWfjsO+PfjIqOFo9lNsDtCwbAY/OscbboNZzqlOFPzXhk3P6++PPlwLgclD4hov4ABDBGMXtT9yC1lKLTLHye223QSYkcp58kD8l70j50cslJnzqEoL/s2prDvVmUhJLH6KOjtCViUkMv4KLQSKMQOJNeYPtl0AXuSQ+cRg= Received: from AM4PR05MB3265.eurprd05.prod.outlook.com (10.171.188.154) by AM4SPR01MB270.eurprd05.prod.outlook.com (10.171.191.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.20; Thu, 7 Nov 2019 06:01:26 +0000 Received: from AM4PR05MB3265.eurprd05.prod.outlook.com ([fe80::9940:94f2:db23:aa2c]) by AM4PR05MB3265.eurprd05.prod.outlook.com ([fe80::9940:94f2:db23:aa2c%4]) with mapi id 15.20.2408.028; Thu, 7 Nov 2019 06:01:26 +0000 From: Slava Ovsiienko To: Hideyuki Yamashita CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH 0/7] net/mlx5: support for flow action on VLAN header Thread-Index: AQHVep9vAaM+AojguUG9N9frUX50nqdKSfMAgBYF6oCABHh/AIAAAyGQgAYeM4CABlZewIAB3Z8AgAAAaUCAAAsxgIABUb6ggAAxSYCAAAlQ0IAH3BKAgAGcxgCAAFdJIIAA0YuAgAATSgA= Date: Thu, 7 Nov 2019 06:01:26 +0000 Message-ID: References: <20191106200344.4C2F.17218CA3@ntt-tx.co.jp_1> <20191107134606.4C32.17218CA3@ntt-tx.co.jp_1> In-Reply-To: <20191107134606.4C32.17218CA3@ntt-tx.co.jp_1> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=viacheslavo@mellanox.com; x-originating-ip: [95.67.35.250] x-ms-publictraffictype: Email x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 28ab09f3-f484-4c02-6457-08d76347ed08 x-ms-traffictypediagnostic: AM4SPR01MB270: x-ms-exchange-purlcount: 1 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:5797; x-forefront-prvs: 0214EB3F68 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(366004)(136003)(39850400004)(346002)(376002)(199004)(40764003)(189003)(13464003)(476003)(8936002)(6506007)(14444005)(256004)(71190400001)(30864003)(66066001)(71200400001)(478600001)(81156014)(74316002)(7736002)(81166006)(99286004)(45080400002)(86362001)(11346002)(25786009)(486006)(76116006)(316002)(4326008)(53546011)(2906002)(76176011)(66446008)(305945005)(66476007)(66556008)(186003)(6916009)(64756008)(6116002)(966005)(33656002)(102836004)(5660300002)(6436002)(6306002)(52536014)(446003)(3846002)(9686003)(14454004)(229853002)(26005)(66946007)(7696005)(55016002)(6246003); DIR:OUT; SFP:1101; SCL:1; SRVR:AM4SPR01MB270; H:AM4PR05MB3265.eurprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: SE8BVp/6toda4NO1sltOboIzsNjoM5L6tq//u2tf8VrgLk/LZXq1vS8qqtGcI1dwnjpfJyOF/yUyCTaWlZboqd92cxSCN1cbNI1SQSe60G1K2YMQXfTjDuhYK9DOqAfXRiMgB2iVudRZ82C6+BObr/OiV2lovEE+2jJAPjFVzHAc73nnLPb+aVYnmRvdaVhaJ2upRDZDishrE2brS1ibKBnyT9KwC1qluybDGLeSQ6DDJ14PMR1k7KgwdVaAvxr4dcdU6QySyxe/OpvEd6kx33OA+6sOVunqCCLAiYOcFmu4xB1XI3XK4ksvcdbiOwfCf1Xf7V2lrcl8fu1OSbGf1Fu4Mck+a4k6ZBRQCVUgMvlUg24S3nOxkzZc/nRwkyLJEpmsy0TJeAPSPe3XYjhf7GypU9kh50Ii7xanROJ6VIdWFD5EEmke4Eu0SpLq3Su7 x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: Mellanox.com X-MS-Exchange-CrossTenant-Network-Message-Id: 28ab09f3-f484-4c02-6457-08d76347ed08 X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Nov 2019 06:01:26.5693 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: m5gYkeUP0noOMvacE+qu4GW1oIdimrhi4PJ3gAP8J85vvuXGCCDIdYilQxPs0KiMOhNEzK2X/zeJqSufWDzGPWNnwXVcQl46TsF/gzMlvpw= X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4SPR01MB270 Subject: Re: [dpdk-dev] [PATCH 0/7] net/mlx5: support for flow action on VLAN header X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, Hideyuki > -----Original Message----- > From: Hideyuki Yamashita > Sent: Thursday, November 7, 2019 6:46 > To: Slava Ovsiienko > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 0/7] net/mlx5: support for flow action on > VLAN header >=20 > Hi Slava, >=20 > Thanks for your response. >=20 > 1. As you pointed out, it was configuration issue > (CONFIG_RTE_LIBRTE_MLX5_DEBUG=3Dy)! > When I turned out the configuration, 19.11 rc1 recognized Connect-X5 > corrcetly. No-no, it is not configuration, this just enables debug features and Is hel= pful to locate the reason why ConnectX-5 was not detected on your setup. In release produc= t, of coarse, the CONFIG_RTE_LIBRTE_MLX5_DEBUG must be "n" Or was it just missed "CONFIG_RTE_LIBRTE_MLX5_PMD=3Dy" ? >=20 > Thanks for your help. >=20 > 2. How about the question I put in my previouse email (how to create flow > for entag VLAN tag on not-tagged packet) I'm sorry, I did not express my answer in clear way. This issue is fixed, now you entagging Flow can be created successfully, I = rechecked. Now it works: > > > > testpmd> flow create 0 egress group 1 pattern eth src is > > > > testpmd> BB:BB:BB:BB:BB:BB / end actions of_push_vlan ethertype > > > > testpmd> 0x8100 / of_set_vlan_vid vlan_vid 100 / of_set_vlan_pcp > > > > testpmd> vlan_pcp 3 / end Please, take (coming on Friday) 19.11rc2 and try. With best regards, Slava >=20 > Thanks again. >=20 >=20 > BR, > Hideyuki Yamashita > NTT TechnoCross >=20 > > Hi, Hideyuki > > > > > -----Original Message----- > > > From: Hideyuki Yamashita > > > Sent: Wednesday, November 6, 2019 13:04 > > > To: Slava Ovsiienko > > > Cc: dev@dpdk.org > > > Subject: Re: [dpdk-dev] [PATCH 0/7] net/mlx5: support for flow > > > action on VLAN header > > > > > > Dear Slava, > > > > > > Additional question. > > > When I use testpmd in dpdk-next-net repo, it works in general. > > > However when I use dpdk19.11-rc1, testpmd does not recognize > > > connectX-5 NIC. > > > > It is quite strange, it should be, ConnectX-5 is base Mellanox NIC now. > > Could you, please: > > - configure "CONFIG_RTE_LIBRTE_MLX5_DEBUG=3Dy" in > ./config/common_base > > - reconfigure DPDK and rebuild testpmd > > - run testpmd with --log-level=3D99 --log-level=3Dpmd.net.mlx5:8 (befor= e > > -- separator) > > - see (and provide) the log, where it drops the eth_dev object > > spawning > > > > > > > > Is it correct that ConnectX-5 will be recognized in 19.11 release fin= ally? > > > > It should be recognized in 19.11rc1, possible we have some > > configuration issue, let's have a look at. > > > > > If yes, which release candidate the necessary change will be mergerd > > > and available? > > > > > > BR, > > > Hideyuki Yamashita > > > NTT TechnoCross > > > > > > > > > > Dear Slava, > > > > > > > > Thanks for your response. > > > > > > > > Inputting other flows failed while some flows are created. > > > > Please help on the following two cases. > > > > > > > > 1) I would like to detag vlan tag which has specific destionation > > > > MAC address. No condition about vlan id value. > > > > > > > > testpmd> flow create 0 ingress group 1 pattern eth dst is > > > > testpmd> AA:AA:AA:AA:AA:AA / vlan / any / end actions of_pop_vlan > > > > testpmd> / queue index 1 / end > > > > Caught error type 10 (item specification): VLAN cannot be empty: > > > > Invalid argument > > > > testpmd> flow create 0 ingress group 1 pattern eth dst is > > > > testpmd> AA:AA:AA:AA:AA:AA / vlan vid is 100 / end actions > > > > testpmd> of_pop_vlan / queue index 1 / end > > > > Flow rule #0 created > > > > I'll check, possible this validation reject is imposed by HW > > limitations - it requires the VLAN header presence and (IIRC) VID match= . If > possible - we'll fix. > > > > > > > > > > 2) I would like to entag vlan tag > > > > > > > > testpmd> flow create 0 egress group 1 pattern eth src is > > > > testpmd> BB:BB:BB:BB:BB:BB / end actions of_push_vlan ethertype > > > > testpmd> 0x8100 / of_set_vlan_vid vlan_vid 100 / of_set_vlan_pcp > > > > testpmd> vlan_pcp 3 / end > > > > Caught error type 16 (specific action): cause: 0x7ffdc9d98348, > > > > match on VLAN is required in order to set VLAN VID: Invalid > > > > argument > > > > > > > > It is fixed (and patch Is already merged - > > > https://eur03.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Fpatch > > > es.dpdk.org%2Fpatch%2F62295%2F&data=3D02%7C01%7Cviacheslavo%4 > 0mellan > > > ox.com%7Ca17dfb64b04f430237ff08d7633d7346%7Ca652971c7d2e4d9ba6 > a4d14925 > > > 6f461b%7C0%7C1%7C637086987908448715&sdata=3DUvi1bWYT%2BaHo > TSHkQ8AF6% > > 2FnTx%2FP5UrMqtZ3gAzjqGAA%3D&reserved=3D0), > > let's try coming 19.11rc2. I inserted your Flow successfully on current > Upstream.. > > > > With best regards, Slava > > > > > > > > > > Thanks! > > > > > > > > BR, > > > > Hideyuki Yamashita > > > > NTT TechnoCross > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Hideyuki Yamashita > > > > > > Sent: Thursday, October 31, 2019 11:52 > > > > > > To: Slava Ovsiienko > > > > > > Cc: dev@dpdk.org > > > > > > Subject: Re: [dpdk-dev] [PATCH 0/7] net/mlx5: support for flow > > > > > > action on VLAN header > > > > > > > > > > > > Dear Slava, > > > > > > > > > > > > Your guess is corrrect. > > > > > > When I put flow into Connect-X5, it was successful. > > > > > Very nice. > > > > > > > > > > > > > > > > > General question. > > > > > As we know - general questions are the most hard ones to answer ?= ?. > > > > > > > > > > > Are there any way to input flow to ConnectX-4? > > > > > As usual - with RTE flow API. Just omit dv_flow_en, or specify > > > > > dv_flow_en=3D0 and mlx5 PMD will handle RTE flow API via Verbs > > > > > engine, > > > supported by ConnectX-4. > > > > > > > > > > > In another word, are there any way to activate Verb? > > > > > > And which type of flow is supported in Verb? > > > > > Please, see flow_verbs_validate() routine in the > > > > > mlx5_flow_verbs.c, it shows which RTE flow items and actions are > > > > > actually supported by > > > Verbs. > > > > > > > > > > With best regards, Slava > > > > > > > > > > > > > > > > > > > > > > ----------------------------------------------------------- > > > > > > tx_h-yamashita@R730n10:~/dpdk-next-net/x86_64-native- > linuxapp- > > > > > > gcc/app$ sudo ./te stpmd -c 0xF -n 4 -w 04:00.0,dv_flo= w_en=3D1 > -- > > > socket- > > > > > > mem 512,512 --huge-dir=3D/mnt/h > > > > > > uge1G --log-level port:8 -- -i --portmask=3D0x1 --nb-cores=3D2 > > > > > > --txq=3D16 --rxq=3D16 [sudo] password for tx_h-yamashita: > > > > > > EAL: Detected 48 lcore(s) > > > > > > EAL: Detected 2 NUMA nodes > > > > > > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > > > > > > EAL: Selected IOVA mode 'PA' > > > > > > EAL: Probing VFIO support... > > > > > > EAL: PCI device 0000:04:00.0 on NUMA socket 0 > > > > > > EAL: probe driver: 15b3:1017 net_mlx5 > > > > > > net_mlx5: mlx5.c:1852: mlx5_dev_spawn(): can't query devx port > > > > > > 1 on > > > device > > > > > > mlx5_ 1 > > > > > > > > > > > > Interactive-mode selected > > > > > > > > > > > > testpmd: create a new mbuf pool : > n=3D171456, > > > > > > size=3D2176, socke t=3D0 > > > > > > testpmd: preferred mempool ops selected: ring_mp_mc > > > > > > testpmd: create a new mbuf pool : > n=3D171456, > > > > > > size=3D2176, socke t=3D1 > > > > > > testpmd: preferred mempool ops selected: ring_mp_mc > > > > > > > > > > > > Warning! port-topology=3Dpaired and odd forward ports number, > > > > > > the last > > > port > > > > > > will p air with itself. > > > > > > > > > > > > Configuring Port 0 (socket 0) > > > > > > Port 0: B8:59:9F:C1:4A:CE > > > > > > Checking link statuses... > > > > > > Done > > > > > > testpmd> > > > > > > testpmd> flow create 0 ingress group 1 priority 0 pattern eth > > > > > > testpmd> dst is > > > > > > 00:16:3e:2 e:7b:6a / vlan vid is 1480 / end actions of= _pop_vlan > / > > > queue > > > > > > index 0 / end > > > > > > Flow rule #0 created > > > > > > testpmd> > > > > > > -------------------------------------------------------------- > > > > > > ---- > > > > > > --------------------------- > > > > > > ----------------- > > > > > > > > > > > > BR, > > > > > > Hideyuki Yamashita > > > > > > NTT TechnoCross > > > > > > > > > > > > > Hi, Hideyuki > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: Hideyuki Yamashita > > > > > > > > Sent: Wednesday, October 30, 2019 12:46 > > > > > > > > To: Slava Ovsiienko > > > > > > > > Cc: dev@dpdk.org > > > > > > > > Subject: Re: [dpdk-dev] [PATCH 0/7] net/mlx5: support for > > > > > > > > flow action on VLAN header > > > > > > > > > > > > > > > > Hello Slava, > > > > > > > > > > > > > > > > Thanks for your help. > > > > > > > > I added magic phrase. with chaging PCI number with proper > > > > > > > > one in my > > > > > > env. > > > > > > > > > > > > > > > It changes situation but still result in error. > > > > > > > > > > > > > > > > I used /usertools/dpdk-setup.sh to allocate hugepage > dynamically. > > > > > > > > Your help is appreciated. > > > > > > > > > > > > > > > > I think it is getting closer. > > > > > > > > tx_h-yamashita@R730n10:~/dpdk-next-net/x86_64-native- > > > linuxapp- > > > > > > > > gcc/app$ > > > > > > > > sudo ./testpmd -c 0xF -n 4 -w 03:00.0,dv_flow_en=3D1 > > > > > > > > --socket-mem > > > > > > > > 512,512 - -huge-dir=3D/mnt/h uge1G --log-level port:8 -- -i > > > > > > > > --portmask=3D0x1 --nb-cores=3D2 > > > > > > > > > > > > > > mlx5 PMD supports two flow engines: > > > > > > > - Verbs, this is legacy one, almost no new features are > > > > > > > being added, just > > > > > > bug fixes, > > > > > > > provides slow rule insertion rate, etc. > > > > > > > - Direct Rules, the new one, all new features are being added > here. > > > > > > > > > > > > > > (We had one more intermediate engine - Direct Verbs, it was > > > > > > > dropped, but prefix dv in dv_flow_en remains ??) > > > > > > > > > > > > > > Verbs are supported over all NICs - ConnectX-4,ConnectX-4LX, > > > > > > > ConnectX-5, > > > > > > ConnectX-6, etc. > > > > > > > Direct Rules is supported for NICs starting from ConnectX-5. > > > > > > > "dv_flow_en=3D1" partameter engages Direct Rules, but I see > > > > > > > you run testpmd over 03:00.0 which is ConnectX-4, not > > > > > > > supporting Direct > > > Rules. > > > > > > > Please, run over ConnectX-5 you have on your host. > > > > > > > > > > > > > > As for error - it is not related to memory, rdma core just > > > > > > > failed to create the group table, because ConnectX-4 does > > > > > > > not > > > support DR. > > > > > > > > > > > > > > With best regards, Slava > > > > > > > > > > > > > > > --txq=3D16 --rxq=3D16 > > > > > > > > EAL: Detected 48 lcore(s) > > > > > > > > EAL: Detected 2 NUMA nodes > > > > > > > > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > > > > > > > > EAL: Selected IOVA mode 'PA' > > > > > > > > EAL: Probing VFIO support... > > > > > > > > EAL: PCI device 0000:03:00.0 on NUMA socket 0 > > > > > > > > EAL: probe driver: 15b3:1015 net_mlx5 > > > > > > > > net_mlx5: mlx5.c:1852: mlx5_dev_spawn(): can't query devx > > > > > > > > port > > > > > > > > 1 on device > > > > > > > > mlx5_3 > > > > > > > > > > > > > > > > Interactive-mode selected > > > > > > > > testpmd: create a new mbuf pool : > > > > > > > > n=3D171456, size=3D2176, socket=3D0 > > > > > > > > testpmd: preferred mempool ops selected: ring_mp_mc > > > > > > > > testpmd: create a new mbuf pool : > > > > > > > > n=3D171456, size=3D2176, socket=3D1 > > > > > > > > testpmd: preferred mempool ops selected: ring_mp_mc > > > > > > > > > > > > > > > > Warning! port-topology=3Dpaired and odd forward ports > > > > > > > > number, the last port will pair with itself. > > > > > > > > > > > > > > > > Configuring Port 0 (socket 0) Port 0: B8:59:9F:DB:22:20 > > > > > > > > Checking link statuses... > > > > > > > > Done > > > > > > > > testpmd> flow create 0 ingress group 1 priority 0 pattern > > > > > > > > testpmd> eth dst is 00:16:3e:2e:7b:6a / vlan vid is 1480 / > > > > > > > > testpmd> end actions of_pop_vlan / queue index 0 / end > > > > > > > > Caught error type 1 (cause unspecified): cannot create tabl= e: > > > > > > > > Cannot allocate memory > > > > > > > > > > > > > > > > > > > > > > > > BR, > > > > > > > > Hideyuki Yamashita > > > > > > > > > > > > > > > > > > > > > > > > > > > >=20