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 70E35A04DD; Fri, 30 Oct 2020 09:17:23 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EAB696A44; Fri, 30 Oct 2020 09:17:21 +0100 (CET) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 3AD045B30 for ; Fri, 30 Oct 2020 09:17:19 +0100 (CET) IronPort-SDR: pI38z1TcYZ2RBXng1TWVmzCK63rHaugwmTTL15BRCvLET5JE3W3wm11OqMAB7Edj/451cu/TIv 0JOf0zlb1t4g== X-IronPort-AV: E=McAfee;i="6000,8403,9789"; a="165078770" X-IronPort-AV: E=Sophos;i="5.77,432,1596524400"; d="scan'208";a="165078770" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Oct 2020 01:17:15 -0700 IronPort-SDR: 3qDKsiRmwtd8gJrf1My+TUzsHYyJwW+BR6Rtn3noxXXXcsUiNBP9pWT7CHszs4aUbGclnObUSi 7RJZMZT1FaUw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,432,1596524400"; d="scan'208";a="469456821" Received: from unknown (HELO localhost.localdomain) ([10.190.210.98]) by orsmga004.jf.intel.com with ESMTP; 30 Oct 2020 01:17:12 -0700 From: Abhinandan Gujjar To: dev@dpdk.org, declan.doherty@intel.com, akhil.goyal@nxp.com, Honnappa.Nagarahalli@arm.com, konstantin.ananyev@intel.com Cc: narender.vangati@intel.com, jerinj@marvell.com, abhinandan.gujjar@intel.com Date: Thu, 29 Oct 2020 04:40:09 +0530 Message-Id: <1603926611-19086-1-git-send-email-abhinandan.gujjar@intel.com> X-Mailer: git-send-email 1.9.1 Subject: [dpdk-dev] [v6 0/2] support enqueue & dequeue callbacks on cryptodev 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" In an eventdev world, multiple workers (with ordered queue) will be working on IPsec ESP processing. The ESP header's sequence number is unique and has to be sequentially incremented in an orderly manner. This rises a need for incrementing sequence number in crypto stage especially in event crypto adapter. By adding a user callback to cryptodev at enqueue burst, the user callback will get executed in the context of event crypto adapter. This helps the application to increment the ESP sequence number atomically and orderly manner. The user callback at the dequeue burst helps IPsec application to take care of ARW processing. v5->v6: -Removed error code in remove callback APIs & cb init -Updated release notes & documentation v4->v5: -Added dequeue callback APIs -Updated documentation -Updated errno and return values -Updated cleanup function v3->v4: -Move callback init and cleanup under dev_configure -Update with memory ordering -Removed extra level of indirection -Add documentation v2->v3: -Moved RCU under the cryptodev APIs -RCU is maintained per queue-pair -Changed name of few variables -Updated callback test with negative cases -Updated with required changes for meson v1->v2: -Moved callback related members to the end of cryptodev struct -Added support for RCU Abhinandan Gujjar (2): cryptodev: support enqueue & dequeue callback functions test: add testcase for crypto enqueue callback app/test/test_cryptodev.c | 135 ++++++++++- config/rte_config.h | 1 + doc/guides/prog_guide/cryptodev_lib.rst | 47 ++++ doc/guides/rel_notes/release_20_11.rst | 9 + lib/librte_cryptodev/meson.build | 2 +- lib/librte_cryptodev/rte_cryptodev.c | 404 +++++++++++++++++++++++++++++++- lib/librte_cryptodev/rte_cryptodev.h | 260 +++++++++++++++++++- lib/librte_cryptodev/version.map | 4 + 8 files changed, 857 insertions(+), 5 deletions(-) -- 1.9.1