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 E21E4A04DD; Mon, 26 Oct 2020 19:52:01 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C63B929C6; Mon, 26 Oct 2020 19:52:00 +0100 (CET) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id E35A91D9E for ; Mon, 26 Oct 2020 19:51:57 +0100 (CET) IronPort-SDR: 46ZGitFO3QPTHFdGmDAfpnA/u6xH+q6sHMp9UDqfHAx1MsQ/MaFsPY1nx59n/mqhbp5SVEk6t7 wVWYRXOLz7bQ== X-IronPort-AV: E=McAfee;i="6000,8403,9786"; a="168097300" X-IronPort-AV: E=Sophos;i="5.77,420,1596524400"; d="scan'208";a="168097300" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Oct 2020 11:51:56 -0700 IronPort-SDR: ccgog0WIB8yUus3cmecQq0CIMO0rhYqY+YBF28a82GV6Bb1ICX2tvB0N6amVOsgHmXQYJ+G33g v8jzvjt22ViQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,420,1596524400"; d="scan'208";a="303501251" Received: from unknown (HELO localhost.localdomain) ([10.190.210.98]) by fmsmga008.fm.intel.com with ESMTP; 26 Oct 2020 11:51:53 -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: Sun, 25 Oct 2020 15:14:47 +0530 Message-Id: <1603619090-118652-1-git-send-email-abhinandan.gujjar@intel.com> X-Mailer: git-send-email 1.9.1 Subject: [dpdk-dev] [v4 0/3] support enqueue 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. 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 (3): cryptodev: support enqueue callback functions test: add testcase for crypto enqueue callback doc: add enqueue callback APIs app/test/test_cryptodev.c | 133 +++++++++++++- config/rte_config.h | 1 + doc/guides/prog_guide/cryptodev_lib.rst | 22 +++ doc/guides/rel_notes/release_20_11.rst | 5 + lib/librte_cryptodev/meson.build | 2 +- lib/librte_cryptodev/rte_cryptodev.c | 230 +++++++++++++++++++++++++ lib/librte_cryptodev/rte_cryptodev.h | 158 ++++++++++++++++- lib/librte_cryptodev/rte_cryptodev_version.map | 2 + 8 files changed, 549 insertions(+), 4 deletions(-) -- 1.9.1