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 EDFE4A0526 for ; Wed, 22 Jul 2020 19:24:02 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4F7BC1BFCA; Wed, 22 Jul 2020 19:24:02 +0200 (CEST) Received: from mx0b-002e3701.pphosted.com (mx0b-002e3701.pphosted.com [148.163.143.35]) by dpdk.org (Postfix) with ESMTP id 45A04199BC for ; Wed, 22 Jul 2020 19:24:01 +0200 (CEST) Received: from pps.filterd (m0150244.ppops.net [127.0.0.1]) by mx0b-002e3701.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 06MHIeN9026256 for ; Wed, 22 Jul 2020 17:24:00 GMT Received: from g9t5009.houston.hpe.com (g9t5009.houston.hpe.com [15.241.48.73]) by mx0b-002e3701.pphosted.com with ESMTP id 32ekuhubdb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 22 Jul 2020 17:23:59 +0000 Received: from G2W6311.americas.hpqcorp.net (g2w6311.austin.hp.com [16.197.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by g9t5009.houston.hpe.com (Postfix) with ESMTPS id 6C2DB73 for ; Wed, 22 Jul 2020 17:23:59 +0000 (UTC) Received: from G9W9209.americas.hpqcorp.net (16.220.66.156) by G2W6311.americas.hpqcorp.net (16.197.64.53) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 22 Jul 2020 17:23:59 +0000 Received: from NAM04-SN1-obe.outbound.protection.outlook.com (15.241.52.12) by G9W9209.americas.hpqcorp.net (16.220.66.156) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 22 Jul 2020 17:23:58 +0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Q65bCNCyGrhVUg/zU6FhHRK3hxVIYqeNkFH5lckuiNEgdUDwOqjsKbVpWkH+QJLnRx7h/t9mDugAu5ydbIh+HQ8/+laoKdMBdhQOao9R2GkfEFw4YIUbAa3Q1O7SiQP1j99S6zvGBDxSyvN2jM0PEDNy9tKUU+ludk7JTEpaS2NKxO3vrT1HV4xfgx/PYTgqlzOLp3AlKdemtQLTt6XRZQp4LLfJWZ4lOcSkuHh1jk0aj3dQTqMxRasbIt8SdHZy4teH3U8jD9q+B0hB6yP0lo/kG/BEeE6CxZGqexZnfsPTssrVI4zzOxurkXt8rRq8EqR67hQ+0A6VX+Due5Y0lQ== 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=RS3gdXqm7clCyvl9Rjnz5Atq+7FvjTm/0veXbA0uCyI=; b=mukw0NZoataU6xRMzcCz4YEbmMjl/jneOH0rS1aM24FEudaKJiZlpeqpewdslItBSoR8s/72rvqyA/aVwUtxgOu3kWRyJ+DtTX79DytnnN9NF56wtWcxDWOsaAvD3BXa0xj5ug0dYUgwoh7nt6QPPLK5WDt/Xe3SE3Y2sNxzyDTGEySlNOIN9tPk6WnsW/1RJvMHttJqcDqyWJ+pM9u0M8rQc9T4uGRQe1Rpig3SwucHlAKW8FJfcdYSlF9qKkvF3BzTRA3IYmUi+XhmpbWyt3Gwlr/+MsuiIbKpW6iozm8WFUEIjZWAjr8ce234ONiRWmt7m9e3uEZRmMsq8glA1w== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=hpe.com; dmarc=pass action=none header.from=hpe.com; dkim=pass header.d=hpe.com; arc=none Received: from AT5PR8401MB0545.NAMPRD84.PROD.OUTLOOK.COM (2a01:111:e400:741f::19) by AT5PR8401MB0452.NAMPRD84.PROD.OUTLOOK.COM (2a01:111:e400:741f::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3195.25; Wed, 22 Jul 2020 17:23:57 +0000 Received: from AT5PR8401MB0545.NAMPRD84.PROD.OUTLOOK.COM ([fe80::dd2b:9be5:6544:7fb0]) by AT5PR8401MB0545.NAMPRD84.PROD.OUTLOOK.COM ([fe80::dd2b:9be5:6544:7fb0%12]) with mapi id 15.20.3195.026; Wed, 22 Jul 2020 17:23:57 +0000 From: "Joshi, Venkatesh" To: "Trahe, Fiona" , "users@dpdk.org" Thread-Topic: DPDK-19.11 : IPSEC-SECGW tests not successful Thread-Index: AdZf+InBxsdbQ2XmRVycQpy+BoUEVwAI88QwAAlEwFAAADg58AACbNwg Date: Wed, 22 Jul 2020 17:23:57 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: intel.com; dkim=none (message not signed) header.d=none;intel.com; dmarc=none action=none header.from=hpe.com; x-originating-ip: [106.51.30.176] x-ms-publictraffictype: Email x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 63021665-2cdb-4e85-bc12-08d82e640458 x-ms-traffictypediagnostic: AT5PR8401MB0452: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:773; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: MGakG02uBl/c1mbkIjHLQi3/UYiRDjz54Q5ggigXaJu7RHTi5DsV/qf1JRk6BwrxyFVr7ui/licOCMmBSAPCbVjz7zaS/jFLvADZ09QV4E72Dzx6Jh0+0XoOeCBFjKbuewH+OjkNEIADqOoJfr72kvuvWaOi4neLMz02Ke7ut2kKqFo/Em8AqPbcxycLZ8NDK1zC8zNPs1FgKEdgi/aVx5zrPUX12goJe98RgcD3fnETKhQ/jNS15kITAELtmp/P8H2b5KnT5lvQIN90HgoWliliid6toMVPiwvezE7q1YEUqWMssushjYlpo/MgHcfw2YWIkrLFHCW/bA9js+AZKkcnqSNEEapivuutULXYFBGhQrxVnJ2udMRj6aqjGmZ5C+TkFob9SDDGxQfNDpQVPw== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AT5PR8401MB0545.NAMPRD84.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFTY:; SFS:(396003)(366004)(39860400002)(346002)(376002)(136003)(55016002)(316002)(5660300002)(186003)(71200400001)(2906002)(83380400001)(53546011)(66446008)(9686003)(66556008)(8936002)(66476007)(64756008)(66946007)(52536014)(7696005)(8676002)(6506007)(76116006)(55236004)(33656002)(26005)(110136005)(478600001)(86362001); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata: i/6LbgP8scfC30nEBz/bW2/CngMgkElk+0Ly3Q9d7tjlxX2wRtwlaRWppnSrVgwVRAmWeryKRpsZj9koJIwUkTbSBhH5QfyrL8GkIrDEgIjvyLhlLun5FMWBGHNmXMfRNmKzXZ4Arp3ou7C1Tw2ZfvR3eCxEBJCJi0dX575hoofhZ56CrzcMdssCoVv6VClmu+Sn4NwWYR39TCFLp250Nvv9ytr4EiAcsdIyF36phzwH0tfygSR6uZ9LwDq1125TdixMFWahHCQa8LQF8bX7FNKEOx+uvT42LEFNodan0gbQZ5GwQOiinLv2JBkbefPzo6oCNqswfLy2X5ngVSt9u0ZXMqsMCb9cwTQiIOs3F6EmhgOk0sS+M0xfslVUriLmqUf8O0gFZICoo9LQeqXYm79vt2d8C3LGxRIZuzSryZ5NavWV9HhNLW1nv0YCOVZs56XWlvMtT54+yv6QWX8zCmRI1m5KO01wDiTsKb2QphjpsfpIV26b7RfUXYXwFJMW x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="us-ascii" X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: AT5PR8401MB0545.NAMPRD84.PROD.OUTLOOK.COM X-MS-Exchange-CrossTenant-Network-Message-Id: 63021665-2cdb-4e85-bc12-08d82e640458 X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jul 2020 17:23:57.6047 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: +y8bypZcM+cFjOKDr2KMJPYWBLy3oDwOeSxZeXhiuhIj/m1EMCb+JGe0OIei1slnZC9nzLiO0I1z9LC4lHYelQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: AT5PR8401MB0452 X-OriginatorOrg: hpe.com Content-Transfer-Encoding: quoted-printable X-Proofpoint-UnRewURL: 0 URL was un-rewritten MIME-Version: 1.0 X-HPE-SCL: -1 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-22_10:2020-07-22, 2020-07-22 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 bulkscore=0 suspectscore=0 mlxlogscore=999 priorityscore=1501 malwarescore=0 adultscore=0 clxscore=1015 phishscore=0 impostorscore=0 lowpriorityscore=0 mlxscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2007220113 Subject: Re: [dpdk-users] DPDK-19.11 : IPSEC-SECGW tests not successful 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 Fiona, Could you elaborate on this? Here is my understanding of the same - just to run it by you: * I have two Intel boards with the C627 PCH (Lewisburg) on each. * 67:01.0 - This the VF for the QAT engine with PF 67:00.0. * I put the same VF on each board for the whitelist. I assumed that they ar= e two different devices and it shouldn't matter what device I chose. Do I need to use a different bdf on each board?=20 I have no issues in changing to 68:01.0 on board 2. I tried with that too b= ut the results are the same. Also, the fw_counters don't get updated while traffic is running. Does this= mean that the QAT is not exercised? # cat /sys/kernel/debug/qat_c6xx_0000\:68\:00.0/fw_counters +------------------------------------------------+ | FW Statistics for Qat Device | +------------------------------------------------+ | Firmware Requests [AE 0]: 1 | | Firmware Responses[AE 0]: 1 | +------------------------------------------------+ | Firmware Requests [AE 1]: 1 | | Firmware Responses[AE 1]: 1 | +------------------------------------------------+ | Firmware Requests [AE 2]: 1 | | Firmware Responses[AE 2]: 1 | +------------------------------------------------+ | Firmware Requests [AE 3]: 1 | | Firmware Responses[AE 3]: 1 | +------------------------------------------------+ | Firmware Requests [AE 4]: 1 | | Firmware Responses[AE 4]: 1 | +------------------------------------------------+ | Firmware Requests [AE 5]: 1 | | Firmware Responses[AE 5]: 1 | +------------------------------------------------+ | Firmware Requests [AE 6]: 1 | | Firmware Responses[AE 6]: 1 | +------------------------------------------------+ | Firmware Requests [AE 7]: 1 | | Firmware Responses[AE 7]: 1 | +------------------------------------------------+ | Firmware Requests [AE 8]: 1 | | Firmware Responses[AE 8]: 1 | +------------------------------------------------+ | Firmware Requests [AE 9]: 1 | | Firmware Responses[AE 9]: 1 | +------------------------------------------------+ Regards, Venkatesh -----Original Message----- From: Trahe, Fiona [mailto:fiona.trahe@intel.com]=20 Sent: Wednesday, July 22, 2020 9:40 PM To: Joshi, Venkatesh ; users@dpdk.org Cc: Trahe, Fiona Subject: RE: DPDK-19.11 : IPSEC-SECGW tests not successful Maybe just a typo - but you're using the same bdf on both boards - should b= e 68.01.0 on board 2 ? > -----Original Message----- > From: Joshi, Venkatesh > Sent: Wednesday, July 22, 2020 5:05 PM > To: Trahe, Fiona ; users@dpdk.org > Subject: RE: DPDK-19.11 : IPSEC-SECGW tests not successful >=20 > Hi Fiona, >=20 > Here are the command-lines: >=20 >=20 > For the Intel Board 1: > ------------------------- >=20 > ./build/ipsec-secgw -l 1 -n 4 -w b3:00.0 -w b3:00.1 -w 67:01.0 -- -P=20 > -p 0x3 -u 1 --config=3D"(0,0,1),(1,0,1)" -f ./ep0-intel-board1.cfg >=20 > ep0-intel-board1.cfg: > ------------------------- > #SP IPv4 rule - for outgoing (to crb-3) sp ipv4 out esp protect 1000=20 > pri 5 dst 40.1.1.0/24 sport 0:65535 dport 0:65535 >=20 > #SA rules > sa out 1000 cipher_algo aes-128-cbc cipher_key=20 > a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:\ > a0:a0:a0:a0 auth_algo sha1-hmac auth_key=20 > a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:\ > a0:a0:a0:a0:a0:a0:a0:a0 mode ipv4-tunnel src 20.1.1.50 dst 20.1.1.20 >=20 > #SP IPv4 rule - for incoming (to IXIA) sp ipv4 in esp protect 1010 pri=20 > 5 dst 20.1.1.50/32 src 20.1.1.20/32 sport 0:65535 dport 0:65535 >=20 > #SA rules > sa in 1010 cipher_algo aes-128-cbc cipher_key=20 > a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:\ > a0:a0:a0:a0 auth_algo sha1-hmac auth_key=20 > a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:\ > a0:a0:a0:a0:a0:a0:a0:a0 mode ipv4-tunnel src 20.1.1.20 dst 20.1.1.50 >=20 >=20 > #Routing rules > rt ipv4 dst 20.1.1.20/32 port 1 > rt ipv4 dst 30.1.1.10/32 port 0 >=20 >=20 > For the Intel Board 2: > ------------------------- > ./build/ipsec-secgw -l 1 -n 4 -w 17:00.0 -w 17:00.1 -w 67:01.0 -- -P=20 > -p 0x3 -u 1 --config=3D"(0,0,1),(1,0,1)" -f ./ep1-intel-board2.cfg >=20 > ep1-intel-board2.cfg: > ---------------------- > #SP IPv4 rule - for outgoing (from IXIA) sp ipv4 out esp protect 1010=20 > pri 1 dst 30.1.1.0/24 sport 0:65535 dport 0:65535 >=20 > #SA rules > sa out 1010 cipher_algo aes-128-cbc cipher_key=20 > a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:\ > a0:a0:a0:a0 auth_algo sha1-hmac auth_key=20 > a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:a0:\ > a0:a0:a0:a0:a0:a0:a0:a0 mode ipv4-tunnel src 20.1.1.20 dst 20.1.1.50 >=20 > #Routing rules > rt ipv4 dst 20.1.1.50/32 port 1 >=20 >=20 >=20 >=20 >=20 >=20 > Regards, > Venkatesh >=20 >=20 > -----Original Message----- > From: Trahe, Fiona [mailto:fiona.trahe@intel.com] > Sent: Wednesday, July 22, 2020 5:15 PM > To: Joshi, Venkatesh ; users@dpdk.org > Cc: Trahe, Fiona > Subject: RE: DPDK-19.11 : IPSEC-SECGW tests not successful >=20 > Have you tried using --log-level=3D8 (or =3D"qat,8") on your process comm= andline? > In conjunction with rebuilding with > CONFIG_RTE_LOG_DP_LEVEL=3DRTE_LOG_DEBUG > this should show if any cryptodev ops are being sent to QAT PMD. >=20 > Something else to try would be - can you run either=20 > dpdk-test-crypto-perf or the unit test application - just to validate=20 > that the process can run crypto on QAT PMD ok. > Your setup for QAT looks ok. >=20 > Also could you share the command-line you're using for each process pleas= e. >=20 >=20 > > -----Original Message----- > > From: users On Behalf Of Joshi, Venkatesh > > Sent: Wednesday, July 22, 2020 8:51 AM > > To: users@dpdk.org > > Subject: [dpdk-users] DPDK-19.11 : IPSEC-SECGW tests not successful > > > > Hi, > > > > I'm not able to successfully run the IPSEC-SECGW tests with=20 > > DPDK-19.11. I have followed the guide published at doc.dpdk.org but sti= ll not able to get things right. > > > > Please help me figure out what could be wrong. > > > > Here are the setup details: > > > > Network Diagram: > > ------------------ > > XL710 = XL 710 > > |---------------------|Port 1 IPSEC Tunnel = Port 1|----------------------| > > | Intel board 1 |<--------------------------------= ------>| Intel board 2 | > > |---------------------| = |----------------------| > > Port 0 ^ = ^ Port 0 (XL710) > > (XL710) | = | > > | |--------------------------------| = | > > -------->|7 IXIA 4|<-= ------------------ > >=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 > > |--------------------------------| > > > > * Linux kernel: 4.14 > > * DPDK version: 19.11 > > * All ports are 40G ports (XL710 NICs) > > * The intel board is: Intel(R) Xeon(R) Gold 5220 CPU > > - has a single socket, 18 cores, 2 threads per=20 > > core > > * The QAT card: C62x > > > > > > Issue: > > -------- > > * Traffic is sent from IXIA Port 4 to IXIA port 7: > > - This is IP/UDP traffic of size 1024 bytes > > - The dst mac is set to the MAC of port 0 of the XL710 NIC of Intel = board 2 > > - The src ip: 40.1.1.10, dst ip: 30.1.1.10 > > - No packets are received on IXIA Port 7 > > - On further debugging: Packets are not getting forwarded out of the= IPSEC tunnel from Intel board 2. > > > > On Intel board 1: > > ------------------- > > XL710 Port 0: b3:00.0 - bound to vfio-pci > > XL710 Port 1: b3:00.1 - bound to vfio-pci QAT VF: 0000:67:01.0=20 > > 'Device 37c9' drv=3Dvfio-pci > > > > Endpoint 0 config file: attached > > Command-line and output file: attached > > > > On Intel board 2: > > ------------------- > > XL710 Port 0: 17:00.0 - bound to vfio-pci > > XL710 Port 1: 17:00.1 - bound to vfio-pci QAT VF: 0000:68:01.0=20 > > 'Device 37c9' drv=3Dvfio-pci > > > > Endpoint 1 config file: attached > > Command-line and output file: attached > > > > > > DPDK: > > ------- > > - config has the following set: > > CONFIG_RTE_LIBRTE_PMD_QAT=3Dy > > CONFIG_RTE_LIBRTE_PMD_QAT_SYM=3Dy > > > > QAT driver version: qat1.7.l.4.9.0-00008 > > ------------------------------------------- > > Makefile has: ICP_SRIOV_AM=3D1 > > ./configure --enable-icp-sriov=3Dhost > > > > > > Please let me know if any additional information is required. > > > > > > Regards, > > Venkatesh > > > > > > -------------- next part -------------- An embedded and=20 > > charset-unspecified text was scrubbed... > > Name: intel-board1-cmdline-and-output.txt > > URL: 3A__mails.dpdk.org_archives_users_attachments_20200722_3050bab3_attach > ment.txt&d=3DDwIFAg&c=3D=20 > C5b8zRQO1miGmBeVZ2LFWg&r=3D3IqRcCAftcE8t2M39oG2GFhwi2xpH1_aQ5zAqwEWGSE&m > =3DbVttGFqDb=20 > BrrR-0XNypNRdR9q74y5kINxi7lKx2nepg&s=3DuzWkHTzMJ2sddyvpQCSvFjJ921e7w3ocW > Ib_VrRJZxM&e=3D > > > -------------- next part -------------- An embedded and=20 > > charset-unspecified text was scrubbed... > > Name: intel-board2-cmdline-and-output.txt > > URL: 3A__mails.dpdk.org_archives_users_attachments_20200722_3050bab3_attach > ment-=20 > 2D0001.txt&d=3DDwIFAg&c=3DC5b8zRQO1miGmBeVZ2LFWg&r=3D3IqRcCAftcE8t2M39oG2= GFh > wi2xpH1_aQ5z > AqwEWGSE&m=3DbVttGFqDbBrrR- > 0XNypNRdR9q74y5kINxi7lKx2nepg&s=3Di0zTM7t5stYHLY2UVdn9IVYKGZudqptQk6lO_0 > alxNM&e=3D >