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 90433429E2 for ; Tue, 25 Apr 2023 02:51:35 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 019B740A7E; Tue, 25 Apr 2023 02:51:35 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id 4D347400D7 for ; Tue, 25 Apr 2023 02:51:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1682383893; x=1713919893; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=+UHxu4X8d20WWWFhgI00Q/nKZclZeLj3rLRJU5oVDss=; b=FiKtQVyCVe9R5MwwTWLJq05lZoNF7W+nlHzlRSMUa0KdG5HgfWybToKA CTbswSooVTD9K0JkDU44R4EXITsKcfpIFwKeHiR1DyoXGnLSZfEXOE+Im xQ20APX1OY98HQjdI3IrzZ2tDuR+CLGvW0+ZMJuZZMEAhlyUeusSftzPN DgjV1niThq3OWK70s8THwZ4RkcNdw/4YNFMKtK3RsBQJ3uttdZk/w81Jq vsckGG48/OlCGnYtzrwwfuCz8KABvUM3rWgD+gsoV1Z8qdoqtJobHY8tO UOGVMWOhgCx2qLkdddlqr5Bkga/L29kTlCc+8ge1c2vH+47wg0uB/2fxX w==; X-IronPort-AV: E=McAfee;i="6600,9927,10690"; a="349414431" X-IronPort-AV: E=Sophos;i="5.99,223,1677571200"; d="scan'208,217";a="349414431" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Apr 2023 17:51:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10690"; a="804833714" X-IronPort-AV: E=Sophos;i="5.99,223,1677571200"; d="scan'208,217";a="804833714" Received: from fmsmsx602.amr.corp.intel.com ([10.18.126.82]) by fmsmga002.fm.intel.com with ESMTP; 24 Apr 2023 17:51:31 -0700 Received: from fmsmsx610.amr.corp.intel.com (10.18.126.90) by fmsmsx602.amr.corp.intel.com (10.18.126.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Mon, 24 Apr 2023 17:51:31 -0700 Received: from fmsedg602.ED.cps.intel.com (10.1.192.136) by fmsmsx610.amr.corp.intel.com (10.18.126.90) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23 via Frontend Transport; Mon, 24 Apr 2023 17:51:31 -0700 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.109) by edgegateway.intel.com (192.55.55.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.23; Mon, 24 Apr 2023 17:51:31 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=d5Ldt6roeT+Q9sT+vJ6DtodFYZMJCUMiPJi5r4UNoQrJQn0iOLC3cGC6e5VxztewNvIVF4coe32PORxJ+vmPnMqfQ9Tlx1wJ9tBQRWNJZPVJhN5DTWBsfuwnfEeyUnTYekIlD/4wY9psBty760r5fuIeckUhUhX8s0atnEdm5CPlzsChfAQ7XCLZ2X8fTEZ498TMDdaOPAoBVy4tM3lMA/2BOgXX9N5mPYxcIyQfuMCTcY4FDowEKAAwvU6WiO3dRmSdQNwYRr1dyD9/JqDRg5S+havTrZ/Dd6t54K72c5CL77fVC+E5xmGNkgTslm2wIrZqfexcsQ9HyfF7CesioA== 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=RTFimG/siYKtaCmJrAK6miEI28DL/eaPCCI5/iaLydQ=; b=Kd87nFrpB0lEoJlSQ7eG2i7K4N2nIO7Z3YveVonTcrUjmgq4jYwM98mAOJVVyOuBO50I8i2FZI42hhhKN0wMeJLx+gUVpPON/mY56fyO+dBoRlm/oIUaimbAWk/JvzPAjBWdSdk/NNDgMOpq7MVfXKlqV++yNhB/L3gdQiGg09dUyjarSL3S72ueSLnJstdx7gaeq8poIzz+U6BQYIBpYhEDYBjpZ3L1NK9YGvh/zrxOZtp5o9W4cbDXqMcAKQdJU13enecAOn4+wWTcKklRXOyZ8XiWrznFoTJshBO3pOV5GxsmJ2E2vRfFDDrNiLpx0etvZdg1SuE/D9THC+NK9A== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none Received: from SJ0PR11MB4910.namprd11.prod.outlook.com (2603:10b6:a03:2d7::7) by DM4PR11MB7327.namprd11.prod.outlook.com (2603:10b6:8:105::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6319.33; Tue, 25 Apr 2023 00:51:27 +0000 Received: from SJ0PR11MB4910.namprd11.prod.outlook.com ([fe80::4ea1:17de:8c5a:4462]) by SJ0PR11MB4910.namprd11.prod.outlook.com ([fe80::4ea1:17de:8c5a:4462%7]) with mapi id 15.20.6319.033; Tue, 25 Apr 2023 00:51:26 +0000 From: "Tkachuk, Georgii" To: "Zhang, Changchun" , "users@dpdk.org" Subject: RE: does DPDK support QAT C4xxx and how? Thread-Topic: does DPDK support QAT C4xxx and how? Thread-Index: Adl2zGZxUY0LREWhQqWbJBPfTOpcwQAAN/0AAAKLruAAABcIgA== Date: Tue, 25 Apr 2023 00:51:26 +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: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=intel.com; x-ms-publictraffictype: Email x-ms-traffictypediagnostic: SJ0PR11MB4910:EE_|DM4PR11MB7327:EE_ x-ms-office365-filtering-correlation-id: e1d4db36-1d39-44fb-3771-08db45273310 x-ld-processed: 46c98d88-e344-4ed4-8496-4ed7712e255d,ExtAddr x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: +RFllXtp/1Mf8Iaob/zBSkM8mRPC9Rv49Rw6DUassq+/FwXBV8sL65hcJ/XprTdACUNTURRHQxtEsloYikKPAJ9bVu+uk+S5+2Yd0HE4O9Mid+YpZsaUmmWr8uvXMtRDTNThn/0CKt8kgElPQbsfiV84Q3wn+P+WxAdN/cagoVVs3C1uQY59g/Rwy18pMGyGIwhOrmrzUFKbINsmQOgZwzv3BcFfeEwn4gJGA9+i4YMzcMcOS+WwNeWqIYmyJJD5Piw3NpHqy0KvBAogyljKbzd6EdfPBZMuEPxpmHftNLO9j1EznitEsXclfE/uRMyIw+umMHNEzPzP+FfK0YnqDJ2LAIpeGdAs540GVNKldhkwM1QR478puOTJ+i5YZeJ67Ms3HXP0M/SoCGm2hOzSWH9a8Wu7b7GLEE2GiIJYY4BFftc0wsALx2uTNL7OmK5s0h7Ly6fvvb9C5JGjTL6K8Us1GGQ4pbfiYBrrsRkwzYF8vvA9dpWDTAQ9iOTuohx2+5qOEqTf5Sa+NN4ibvS75qxNuyjB1XXapoh4jqXP+cLIpFiJDbU8A6qminFv+cbKLetpjWpg2IzPCRyuPxy568p4J/qR54riIBubS3wVeCKxL/1K4hISrjt8a9wZ4dakhWXbD+rZQJeg+tQjFLoDOETiZTbW7oS7qjT89KFlabY= x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:SJ0PR11MB4910.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230028)(376002)(346002)(366004)(39860400002)(136003)(396003)(451199021)(966005)(38100700002)(122000001)(82960400001)(6506007)(9686003)(53546011)(26005)(55016003)(186003)(8936002)(83380400001)(21615005)(33656002)(2906002)(8676002)(52536014)(5660300002)(478600001)(7696005)(166002)(71200400001)(38070700005)(110136005)(316002)(66556008)(76116006)(64756008)(41300700001)(66446008)(66946007)(86362001)(66476007)(32563001); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?2IhPPfSALB8Ey3p/+qxgnM1uXkM/bKDpTmNh1f7KxSeAUbL4xekMry4sO+vY?= =?us-ascii?Q?sz9T3wWrgaObKJoFuT5XrFEhU+Gbs1zwQPEvsnA66sOG/cI8Yrgs1jAxmiIM?= =?us-ascii?Q?Dz5/iYpI1ZDAS8CCcJnHRI3hho6v1xO5ZOSSKt3kFKWM5npoFYRHHhfYodW1?= =?us-ascii?Q?CDky86Viqec+tJXDlsQIjUPhPhghul8cOG0P9y5gMOqCtzKYF/6C97nlVmnY?= =?us-ascii?Q?ZbOfAyNCFQq1QJywksbupDCRKAXvp1UJgnVrVq9EQckQC8x0JZMHRvi0H20a?= =?us-ascii?Q?GwxuZTfzSOj6ASFO8iJMPmHsca2GvFOTxeTiWqEWdmzz0e0TcetzH6tpJzti?= =?us-ascii?Q?A7DKX+zvdUntbAcVo6/nBCr6ymfHksOIpkc46DnQq7HLZTWRyslJP78Ov3Ho?= =?us-ascii?Q?yDQV0tnx9TEBO1IHddVQs7DO4+0WuKwIXhQ6kFMFFQKyoOtu4jzAyLRbZqlJ?= =?us-ascii?Q?qijjBs2ghuXmKseIoryTZWDX96wF0okAT4m4Zo5/LzHCMNZzgdX+rW41HukO?= =?us-ascii?Q?QVDQBtbm6Zd5oII+j3XLJdb4bSyDObP75Vak8lztNmtdtF7Unx9z1coPHqro?= =?us-ascii?Q?FT+n7eHMVX9uEQncDBa0If25kamVs5uFOq6wQSV91r7IpnPK3tOTaqqBbajn?= =?us-ascii?Q?i+wfn7gNf+rydUhO2fgNpR3UySnwQfWigU6tkDKrIYpCoQAN9dentDkYKhUF?= =?us-ascii?Q?6aN+enpxKqxLNFG8CuLFNz6Fi2ti2+8lyIwuc49n2XtgGTJ6plLJCG1Vxz5i?= =?us-ascii?Q?OyyYFzztqENPks0Nlm4PAVGR/8rv2TT9Me+eAEs5rw/8hufnBRfwiDQeQzmn?= =?us-ascii?Q?DNUPDFzip7ExWD+bH7el/So8IC8UW8Ax4hk8fHd63A7PmzefPTfVvqxwGoGh?= =?us-ascii?Q?vFcm/bHEYIwtdihq4zRgHrKHYD45abCgPO9qP0OUF2drW8sLX2TSHCmQTetM?= =?us-ascii?Q?G7ByqNF3k51znOl3ikGE+iL34S04xPFJfXBKz1z7B7A7ECjlGpcxCIWXha/a?= =?us-ascii?Q?YLxqMV+ruCNOyuLKTBPRHZKx5cX+iNyLPxjSrvZ6jyIXjeF+qEv7mbTkx4ie?= =?us-ascii?Q?hfh1BnBNFkupAxFU6ULSshYcKPDPEuQxsVU4nBMxtnu3VZZoQGbP+OERAkTA?= =?us-ascii?Q?EltctcSMwPGhDTid+8lCJbB+AkJjtFIzR+uWnGZvhg7GciZLPFVRUTH4ACib?= =?us-ascii?Q?P2Y7LpclrmVbfYtq97a4tb6+6t9U7eManeAcPpuZmnboxwJffxhCGjU+qUk+?= =?us-ascii?Q?Ws0mQQn1NN6cxjb4iLMrF9apya2fn/E3UlHp1/sRXNupFJJRrWZJPdks6s6f?= =?us-ascii?Q?W1eUY+qFR0jlmse+0KF18+j8eHbWItZXEASQVEP65MpwOoSl0IuFTI2/VnhQ?= =?us-ascii?Q?gycxamTlcrw4rjI6XcdZPL+dWskIC+PB0z5+KhAaWqtSYc84t0Ey5N8P5z4L?= =?us-ascii?Q?skyOUstbmf/4rIoqHTvg6RsuIOki+LP6MJBbfg63TaNqt6HGxZVecK26px9E?= =?us-ascii?Q?D56ptap/kTWWha2xG9uQCv2ihN7wZ7AuPOGOAGFM574QRR9oPkNjVTAWSDni?= =?us-ascii?Q?vDpxuCldjCNdpVA/awGCq4DmT4AkcmBmyVwjDh6G?= Content-Type: multipart/alternative; boundary="_000_SJ0PR11MB4910D419DC6E0C91C47C13D2F2649SJ0PR11MB4910namp_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: SJ0PR11MB4910.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: e1d4db36-1d39-44fb-3771-08db45273310 X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Apr 2023 00:51:26.5432 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: s+LEsfE3XAVT/lhWj6mqBuPA81Xqkdo0giiqWIywuakOJ1IJncMQbB9lxXewAVtiBM3XxmeelsHrUKMdjHHh10VhP9h0oICW9BfKXR0D5v0= X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM4PR11MB7327 X-OriginatorOrg: intel.com 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 --_000_SJ0PR11MB4910D419DC6E0C91C47C13D2F2649SJ0PR11MB4910namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Device 18a1 is hardware v1.8, so Hardware v1.7/v1.8 version should work. -Georgii From: Changchun Zhang Sent: Monday, April 24, 2023 11:08 AM To: Tkachuk, Georgii ; users@dpdk.org Subject: RE: does DPDK support QAT C4xxx and how? Thanks for confirm. So in your experience, to use C4xxx, are you using the QAT driver of Hardwa= re v2.0 or Hardware v1.7/v1.8 in this page https://www.intel.com/content/ww= w/us/en/developer/topic-technology/open/quick-assist-technology/overview.ht= ml ? Thanks, Changchun (Alex) From: Tkachuk, Georgii > Sent: Monday, April 24, 2023 12:56 PM To: Changchun Zhang >; users@dpdk.org Subject: [External] : RE: does DPDK support QAT C4xxx and how? Hi Changchun, I cannot comment on that driver version pending flag, but from my experienc= e DPDK works with the devices you specified. You should be able to download= the most recent QuickAssist driver, install it with SRIOV support and use = QAT as described in the document you linked. -Georgii From: Changchun Zhang > Sent: Monday, April 24, 2023 9:50 AM To: users@dpdk.org Subject: does DPDK support QAT C4xxx and how? Hi, According to the section 22.3.6 Available kernel drives in https://doc.dpdk= .org/guides-21.11/cryptodevs/qat.html?highlight=3Dqat , the "Driver/ver" column for d= evice C4xxx is still in release pending status. Yes No No 3 C4xxx p qat_c4xxx c4xxx 18a0 1 18a1 128 Does it mean that DPDK still cannot run acceleration with QAT C4xxx device?= If it can, how does it work? Thanks Changchun --_000_SJ0PR11MB4910D419DC6E0C91C47C13D2F2649SJ0PR11MB4910namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Device 18a1 is hardware v1.8, so Hardware v1.7/v1.8 = version should work.

 

-Georgii

 

From: Changchun Zhang <changchun.zhang@ora= cle.com>
Sent: Monday, April 24, 2023 11:08 AM
To: Tkachuk, Georgii <georgii.tkachuk@intel.com>; users@dpdk.o= rg
Subject: RE: does DPDK support QAT C4xxx and how?

 

Tha= nks for confirm.

So = in your experience, to use C4xxx, are you using the QAT driver of Hardware = v2.0 or Hardware v1.7/v1.8 in this page https://www.intel.com/content/www/us/en/developer/topic-technology/open/qui= ck-assist-technology/overview.html ?

 

 

Thanks,<= /span>

Changchun (Alex)<= /o:p>

 

From: Tkachuk, Georgii <georgii.tkachuk@intel.com>
Sent: Monday, April 24, 2023 12:56 PM
To: Changchun Zhang <changchun.zhang@oracle.com>; users@dpdk.org
Subject: [External] : RE: does DPDK support QAT C4xxx and how?<= /o:p>

 

Hi Changchun,

 

I cannot comment on that driver version pending flag= , but from my experience DPDK works with the devices you specified. You sho= uld be able to download the most recent QuickAssist driver, install it with= SRIOV support and use QAT as described in the document you linked.

 

-Georgii

 

From: Changchun Zhang <changchun.zhang@oracle.com>
Sent: Monday, April 24, 2023 9:50 AM
To: users@dpdk.org
Subject: does DPDK support QAT C4xxx and how?

 

Hi,

 

According to the section 22.3.6 Available kernel dri= ves in https://doc.dpdk.org/guides-21.11/cryptodevs/qat.html?highlight=3Dqat ,= the “Driver/ver” column for device C4xxx is still in release p= ending status.

 

Yes

No

No

3

C4xxx

p

qat_c4xxx

c4xxx

18a0

1

18a1

128

 

 

Does it mean that DPDK still cannot run acceleration= with QAT C4xxx device? If it can, how does it work?

 

Thanks

Changchun

--_000_SJ0PR11MB4910D419DC6E0C91C47C13D2F2649SJ0PR11MB4910namp_--