From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g4t3426.houston.hpe.com (g4t3426.houston.hpe.com [15.241.140.75]) by dpdk.org (Postfix) with ESMTP id C6B031B651; Wed, 16 May 2018 09:35:34 +0200 (CEST) Received: from G4W9119.americas.hpqcorp.net (exchangepmrr1.us.hpecorp.net [16.210.20.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by g4t3426.houston.hpe.com (Postfix) with ESMTPS id D90AB4F; Wed, 16 May 2018 07:35:33 +0000 (UTC) Received: from G1W8107.americas.hpqcorp.net (2002:10c1:483b::10c1:483b) by G4W9119.americas.hpqcorp.net (2002:10d2:14d6::10d2:14d6) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 16 May 2018 07:35:29 +0000 Received: from NAM01-BY2-obe.outbound.protection.outlook.com (15.241.52.13) by G1W8107.americas.hpqcorp.net (16.193.72.59) with Microsoft SMTP Server (TLS) id 15.0.1178.4 via Frontend Transport; Wed, 16 May 2018 07:35:29 +0000 Received: from TU4PR8401MB0655.NAMPRD84.PROD.OUTLOOK.COM (10.169.44.149) by TU4PR8401MB1136.NAMPRD84.PROD.OUTLOOK.COM (10.169.48.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Wed, 16 May 2018 07:35:27 +0000 Received: from TU4PR8401MB0655.NAMPRD84.PROD.OUTLOOK.COM ([fe80::20d8:b9aa:e9a7:9470]) by TU4PR8401MB0655.NAMPRD84.PROD.OUTLOOK.COM ([fe80::20d8:b9aa:e9a7:9470%15]) with mapi id 15.20.0755.018; Wed, 16 May 2018 07:35:26 +0000 From: "DAS, SANJIB" To: "Trahe, Fiona" , "users@dpdk.org" , "dts@dpdk.org" , "test-report@dpdk.org" CC: "Zhang, Roy Fan" , "De Lara Guarch, Pablo" , "DAS, SANJIB" Thread-Topic: Query on ipsec-secgw with crypto algorithm CCM Thread-Index: AdPiIIJ7nmx03B7KTHyDIqvoLFC5OQEkXUQQACR+LRAAEfnCMAAA9RGwAVXiN6A= Date: Wed, 16 May 2018 07:35:26 +0000 Message-ID: References: <348A99DA5F5B7549AA880327E580B4358947982E@IRSMSX103.ger.corp.intel.com> <348A99DA5F5B7549AA880327E580B4358947DD1D@IRSMSX103.ger.corp.intel.com> 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=sanjib.das@hpe.com; x-originating-ip: [1.6.2.218] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; TU4PR8401MB1136; 7:sP+fSIw8IScz6zh/CKQ8cxBEPLfW+QtPZkdLCPokRHJEQq+NT3tOXVPRMnJdR5p1E6zaQMGwy5pQ2XM4+Y6n8wDaN2CB/eMoU9vePiBF3ju7aq+IjkcpWp/3s0xzljPV9NAPBDkCKSlsl+nc8tU9LfYQkY02tndA97PsBbOCdNcCDmO9Z4CnBS+LuhkLin07YdT1ma5PINBd0J2mTfazeKzDndPC5pS+o9S4+50DOezzc0dGTJBJa1hxEjlBDpjM x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR; x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10019020)(376002)(396003)(39860400002)(39380400002)(346002)(366004)(13464003)(199004)(189003)(66066001)(5250100002)(305945005)(6246003)(105586002)(476003)(6506007)(446003)(53546011)(74316002)(93886005)(6436002)(97736004)(186003)(53346004)(2501003)(7696005)(347745004)(478600001)(33656002)(7736002)(76176011)(6306002)(4326008)(14454004)(2201001)(229853002)(2906002)(86362001)(9686003)(110136005)(54906003)(8676002)(68736007)(81156014)(5660300001)(2900100001)(53936002)(102836004)(81166006)(99286004)(55016002)(16799955002)(6116002)(3846002)(486006)(8936002)(106356001)(316002)(3280700002)(3660700001)(25786009)(26005); DIR:OUT; SFP:1102; SCL:1; SRVR:TU4PR8401MB1136; H:TU4PR8401MB0655.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:(222181515654134); BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(5600026)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7153060)(7193020); SRVR:TU4PR8401MB1136; x-ms-traffictypediagnostic: TU4PR8401MB1136: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(261408538637735)(227479698468861)(222181515654134)(228905959029699); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93001095)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(20161123560045)(20161123558120)(20161123564045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:TU4PR8401MB1136; BCL:0; PCL:0; RULEID:; SRVR:TU4PR8401MB1136; x-forefront-prvs: 0674DC6DD3 received-spf: None (protection.outlook.com: hpe.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: WzCpOSYzkOqhY58vU2g5AbB14Dl9pZ3hyQwNDcyyC++1rIybF/R9N7VzpDYwqQLTvNxX3pIr4GYngMuR6Wgl3WVkSAhb5cuj/fhshNAfuOAPwxrze9JkS6ikYLRtG9C+eg/X7tHbvz2hshcp7QP3UJn0ZuOxgFPamgboxsrIrIBTtjH472SQqyjwH0BTdGVA spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: 3a9c48f3-9e8c-4286-208a-08d5baff97da X-MS-Exchange-CrossTenant-Network-Message-Id: 3a9c48f3-9e8c-4286-208a-08d5baff97da X-MS-Exchange-CrossTenant-originalarrivaltime: 16 May 2018 07:35:26.8781 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc X-MS-Exchange-Transport-CrossTenantHeadersStamped: TU4PR8401MB1136 X-OriginatorOrg: hpe.com X-Mailman-Approved-At: Thu, 17 May 2018 18:41:06 +0200 Subject: Re: [dpdk-users] Query on ipsec-secgw with crypto algorithm CCM 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: , X-List-Received-Date: Wed, 16 May 2018 07:35:35 -0000 Hi Fiona, One query with dpsk-17.11.2 ipsec-secgw. I do see API ixgbe_crypto_enable_ipsec() returning me error for both rx/tx = (dev_conf.rxmode.offloads/dev_conf.txmode.offloads) offload on my target X8= 6 system. It fails to read value whatever it writes either on IXGBE_SECRXCTRL or IXGB= E_SECTXCTRL. I am currently debugging this issue, but if I ignore these errors it contin= ues & I can see its handling packets also. Does ignoring these errors mean simply its not enabling hw offloads for bot= h rx/tx?=20 Is my understanding correct? Other than that does it have any other side ef= fect?=20 Thanks, Sanjib -----Original Message----- From: DAS, SANJIB=20 Sent: Wednesday, May 9, 2018 5:48 PM To: 'Trahe, Fiona' ; users@dpdk.org; dts@dpdk.org; t= est-report@dpdk.org Cc: Zhang, Roy Fan ; De Lara Guarch, Pablo Subject: RE: Query on ipsec-secgw with crypto algorithm CCM Thanks a lot Fiona. It worked. Thanks, Sanjib my page-0 wiki -----Original Message----- From: Trahe, Fiona [mailto:fiona.trahe@intel.com] Sent: Wednesday, May 9, 2018 5:22 PM To: DAS, SANJIB ; users@dpdk.org; dts@dpdk.org; test-re= port@dpdk.org Cc: Zhang, Roy Fan ; De Lara Guarch, Pablo ; Trahe, Fiona Subject: RE: Query on ipsec-secgw with crypto algorithm CCM CCM aead-iv-size should be between 7 and 13, you're setting to 16. See drivers/crypto/openssl/rte_openssl_pmd_ops.c for openssl capabilities > -----Original Message----- > From: DAS, SANJIB [mailto:sanjib.das@hpe.com] > Sent: Wednesday, May 9, 2018 4:19 AM > To: Trahe, Fiona ; users@dpdk.org;=20 > dts@dpdk.org; test-report@dpdk.org > Cc: Zhang, Roy Fan ; De Lara Guarch, Pablo=20 > ; DAS, SANJIB > Subject: RE: Query on ipsec-secgw with crypto algorithm CCM >=20 > Thanks Fiona, >=20 > Recently I was trying with "dpdk-test-crypto-perf" application & PMD as = openssl. > But I do see it fails for CCM (dpdk-17.11.2). This API fails=20 > rte_cryptodev_sym_capability_check_aead(). It all works fine with GCM. >=20 >=20 > I used this command >=20 > ./dpdk-test-crypto-perf -l 1-2 --vdev crypto_openssl -w 0000:00:00.0 > -- --devtype crypto_openssl --aead- algo aes-ccm --aead-key-sz 16=20 > --aead-iv-sz 16 --aead-op encrypt --aead-aad-sz 16 --digest-sz 16=20 > --optype aead --silent --ptest throughput --total-ops 1000000 >=20 > Not sure if others too faced this issue. >=20 > Thanks, > Sanjib >=20 > my page-0 wiki >=20 >=20 > -----Original Message----- > From: Trahe, Fiona [mailto:fiona.trahe@intel.com] > Sent: Tuesday, May 8, 2018 3:26 PM > To: DAS, SANJIB ; users@dpdk.org; dts@dpdk.org;=20 > test-report@dpdk.org > Cc: Zhang, Roy Fan ; De Lara Guarch, Pablo=20 > > Subject: RE: Query on ipsec-secgw with crypto algorithm CCM >=20 > Hi Sanjib, >=20 > Copying Pablo who added unit tests for it in this commit - this should=20 > give you an example of how to get it working: > 77a217a19bb72860e26b9aefb19dce92239e0820 >=20 > Also copying Fan who added CCM to aesni_mb PMD. >=20 > Fiona >=20 > > -----Original Message----- > > From: users [mailto:users-bounces@dpdk.org] On Behalf Of DAS, SANJIB > > Sent: Wednesday, May 2, 2018 3:21 PM > > To: users@dpdk.org; dts@dpdk.org; test-report@dpdk.org > > Cc: DAS, SANJIB > > Subject: [dpdk-users] Query on ipsec-secgw with crypto algorithm CCM > > > > Hello team, > > > > I am currently executing performance testing using ipsec-secgw=20 > > application for different crypto > algorithms. > > I was able to execute the tests for crypto algorithms CBC & GCM, but=20 > > as such dint find much pointers on CCM. From ipsec-secgw sample=20 > > application source code (DPDK-18.02.1) also it looks CCM support is=20 > > not there. Could you kindly share your comments on that. Can we=20 > > actually execute ipsec-secgw > application for crypto algorithm CCM? > > >=20 > > Thanks, > > Sanjib > > > > my page-0 > > wiki > i_ > > space> > > > > > > >=20