Message ID | 20221001004213.2911114-1-vfialko@marvell.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7D2C1A00C4; Sat, 1 Oct 2022 02:42:25 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2C0F740684; Sat, 1 Oct 2022 02:42:25 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by mails.dpdk.org (Postfix) with ESMTP id 2B8064003F for <dev@dpdk.org>; Sat, 1 Oct 2022 02:42:23 +0200 (CEST) Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 28UDKLfo029039; Fri, 30 Sep 2022 17:42:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type; s=pfpt0220; bh=DRrNT7zxCGcABmKEXoovSyVZq5MKQ+om1eGEMPGngkI=; b=ZUK31ia6vnJsV87s+vugVk9sBfMDzSYF9Rvkp/kwuQ+Rvi3Sq3pYHdbemjLHiWNX7ra/ 3NiQGAJ/fYkFm5/SazFhR6U+/K8O1ssz+p7NOeKlewGrski/1M9nek8Aqnzn0j3nQLmw Mdbp4v9om81PNmONZmV0vnqkaLc/WWEm6QzT+a30F+tj6+b2b76c5Hz6+5KKWN5a8Ev7 LTZj39SLNZp2gJdG5cid77H0I9BWrGEg3Vc1Vy8SW9Pw4PCZHjundFXUrJTU8Al+gSGi o9mxha+68pd6hzKY3hFxQCq6ir4WPGsPOUqZmnvKaB42EdVb9QX4rJvQ28ZZuX/GM3yt pg== Received: from dc5-exch02.marvell.com ([199.233.59.182]) by mx0a-0016f401.pphosted.com (PPS) with ESMTPS id 3jx18ba3np-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 30 Sep 2022 17:42:21 -0700 Received: from DC5-EXCH01.marvell.com (10.69.176.38) by DC5-EXCH02.marvell.com (10.69.176.39) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Fri, 30 Sep 2022 17:42:20 -0700 Received: from maili.marvell.com (10.69.176.80) by DC5-EXCH01.marvell.com (10.69.176.38) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Fri, 30 Sep 2022 17:42:20 -0700 Received: from localhost.localdomain (unknown [10.28.34.39]) by maili.marvell.com (Postfix) with ESMTP id 671903F7057; Fri, 30 Sep 2022 17:42:18 -0700 (PDT) From: Volodymyr Fialko <vfialko@marvell.com> To: <dev@dpdk.org> CC: <jerinj@marvell.com>, <gakhil@marvell.com>, <anoobj@marvell.com>, <abhinandan.gujjar@intel.com>, Volodymyr Fialko <vfialko@marvell.com> Subject: [PATCH v3 0/2] Vector support for event crypto adapter Date: Sat, 1 Oct 2022 02:42:11 +0200 Message-ID: <20221001004213.2911114-1-vfialko@marvell.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220926113607.1613674-1-vfialko@marvell.com> References: <20220926113607.1613674-1-vfialko@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Proofpoint-ORIG-GUID: DiYJvSzgK43N8Bf-PXow4wSsFRKtZ_pA X-Proofpoint-GUID: DiYJvSzgK43N8Bf-PXow4wSsFRKtZ_pA X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.528,FMLib:17.11.122.1 definitions=2022-09-30_05,2022-09-29_03,2022-06-22_01 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org |
Series |
Vector support for event crypto adapter
|
|
Message
Volodymyr Fialko
Oct. 1, 2022, 12:42 a.m. UTC
Introduce ability to aggregate crypto operations processed by event crypto adapter into single event containing rte_event_vector whose event type is RTE_EVENT_TYPE_CRYPTODEV_VECTOR. * Changes since v1 - Add missing newline/space issues - Add missing error messages - Remove double check of conf input parameter * Changes since v2 - Rebase on top of dpdk-next-eventdev branch - Remove already merged patch Volodymyr Fialko (2): eventdev: introduce event cryptodev vector type crypto/cnxk: add vectorization for event crypto app/test-eventdev/test_perf_common.c | 11 +- app/test/test_event_crypto_adapter.c | 12 +- .../prog_guide/event_crypto_adapter.rst | 23 +- drivers/crypto/cnxk/cn10k_cryptodev_ops.c | 398 ++++++++++++++++-- drivers/crypto/cnxk/cn10k_cryptodev_ops.h | 2 + drivers/crypto/cnxk/cnxk_cryptodev_ops.h | 9 +- drivers/crypto/cnxk/version.map | 1 + drivers/event/cnxk/cn10k_eventdev.c | 33 +- drivers/event/cnxk/cn10k_worker.h | 6 +- drivers/event/cnxk/cn9k_eventdev.c | 10 +- drivers/event/cnxk/cnxk_eventdev.h | 4 +- drivers/event/cnxk/cnxk_eventdev_adptr.c | 17 +- drivers/event/dpaa/dpaa_eventdev.c | 9 +- drivers/event/dpaa2/dpaa2_eventdev.c | 9 +- drivers/event/octeontx/ssovf_evdev.c | 4 +- lib/eventdev/eventdev_pmd.h | 35 +- lib/eventdev/eventdev_trace.h | 6 +- lib/eventdev/rte_event_crypto_adapter.c | 105 ++++- lib/eventdev/rte_event_crypto_adapter.h | 101 ++++- lib/eventdev/rte_eventdev.h | 8 + 20 files changed, 698 insertions(+), 105 deletions(-)
Comments
> Subject: [PATCH v3 0/2] Vector support for event crypto adapter > > Introduce ability to aggregate crypto operations processed by event > crypto adapter into single event containing rte_event_vector whose event > type is RTE_EVENT_TYPE_CRYPTODEV_VECTOR. > > * Changes since v1 > - Add missing newline/space issues > - Add missing error messages > - Remove double check of conf input parameter > > * Changes since v2 > - Rebase on top of dpdk-next-eventdev branch > - Remove already merged patch > Series Acked-by: Akhil Goyal <gakhil@marvell.com> Since there is no response and we are approaching RC1 deadline patches are applied to dpdk-next-crypto with below changes. Updated release notes and removed deprecation notice. Added a build fix because of removal of a macro RTE_FUNC_PTR_OR_ERR_RET. Thanks.
> -----Original Message----- > From: Akhil Goyal <gakhil@marvell.com> > Sent: Saturday, October 1, 2022 9:12 AM > To: Volodymyr Fialko <vfialko@marvell.com>; dev@dpdk.org > Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Anoob Joseph > <anoobj@marvell.com>; Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>; > Volodymyr Fialko <vfialko@marvell.com> > Subject: RE: [PATCH v3 0/2] Vector support for event crypto adapter > > > Subject: [PATCH v3 0/2] Vector support for event crypto adapter > > > > Introduce ability to aggregate crypto operations processed by event > > crypto adapter into single event containing rte_event_vector whose > > event type is RTE_EVENT_TYPE_CRYPTODEV_VECTOR. > > > > * Changes since v1 > > - Add missing newline/space issues > > - Add missing error messages > > - Remove double check of conf input parameter > > > > * Changes since v2 > > - Rebase on top of dpdk-next-eventdev branch > > - Remove already merged patch > > > > Series Acked-by: Akhil Goyal <gakhil@marvell.com> > > Since there is no response and we are approaching RC1 deadline patches are > applied to dpdk-next-crypto with below changes. Hi @Akhil Goyal, Did not we discuss in the call, and I committed to acked the patch by Saturday? You cant call that as no response! > > Updated release notes and removed deprecation notice. > Added a build fix because of removal of a macro RTE_FUNC_PTR_OR_ERR_RET. > > Thanks.
> > > Subject: [PATCH v3 0/2] Vector support for event crypto adapter > > > > > > Introduce ability to aggregate crypto operations processed by event > > > crypto adapter into single event containing rte_event_vector whose > > > event type is RTE_EVENT_TYPE_CRYPTODEV_VECTOR. > > > > > > * Changes since v1 > > > - Add missing newline/space issues > > > - Add missing error messages > > > - Remove double check of conf input parameter > > > > > > * Changes since v2 > > > - Rebase on top of dpdk-next-eventdev branch > > > - Remove already merged patch > > > > > > > Series Acked-by: Akhil Goyal <gakhil@marvell.com> > > > > Since there is no response and we are approaching RC1 deadline patches are > > applied to dpdk-next-crypto with below changes. > Hi @Akhil Goyal, > > Did not we discuss in the call, and I committed to acked the patch by Saturday? > You cant call that as no response! I mentioned in the call that we have RC1 deadline, ack/nack shall be provided as soon as possible. It was agreed that it will come by Friday. I can not spend all of my weekend on a particular series. There are other series also. The patches have been there for about 2 months(V1 was shared on August 4). As per DPDK guidelines, I could merge a patch if there is no response for more than 3 weeks even without asking anybody. I asked out to you just to be courteous on Sep 22. And even after that your responses were pretty slow. You should give ample time for rework to happen before the deadline. From next time onwards, I will not ask for review. You should be proactive within 3 weeks. > > > > Updated release notes and removed deprecation notice. > > Added a build fix because of removal of a macro > RTE_FUNC_PTR_OR_ERR_RET. > > > > Thanks.
> -----Original Message----- > From: Akhil Goyal <gakhil@marvell.com> > Sent: Saturday, October 1, 2022 2:18 PM > To: Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>; Volodymyr Fialko > <vfialko@marvell.com>; dev@dpdk.org > Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Anoob Joseph > <anoobj@marvell.com>; Volodymyr Fialko <vfialko@marvell.com>; > Jayatheerthan, Jay <jay.jayatheerthan@intel.com> > Subject: RE: [PATCH v3 0/2] Vector support for event crypto adapter > > > > > Subject: [PATCH v3 0/2] Vector support for event crypto adapter > > > > > > > > Introduce ability to aggregate crypto operations processed by > > > > event crypto adapter into single event containing rte_event_vector > > > > whose event type is RTE_EVENT_TYPE_CRYPTODEV_VECTOR. > > > > > > > > * Changes since v1 > > > > - Add missing newline/space issues > > > > - Add missing error messages > > > > - Remove double check of conf input parameter > > > > > > > > * Changes since v2 > > > > - Rebase on top of dpdk-next-eventdev branch > > > > - Remove already merged patch > > > > > > > > > > Series Acked-by: Akhil Goyal <gakhil@marvell.com> > > > > > > Since there is no response and we are approaching RC1 deadline > > > patches are applied to dpdk-next-crypto with below changes. > > Hi @Akhil Goyal, > > > > Did not we discuss in the call, and I committed to acked the patch by > Saturday? > > You cant call that as no response! > > I mentioned in the call that we have RC1 deadline, ack/nack shall be provided > as soon as possible. > It was agreed that it will come by Friday. I can not spend all of my weekend on > a particular series. > There are other series also. > The patches have been there for about 2 months(V1 was shared on August 4). > As per DPDK guidelines, I could merge a patch if there is no response for more > than 3 weeks even without asking anybody. > I asked out to you just to be courteous on Sep 22. And even after that your > responses were pretty slow. > You should give ample time for rework to happen before the deadline. But this time few things were not clear. So, we had a call. I would not have sent this mail if I had agreed on Friday. > > From next time onwards, I will not ask for review. You should be proactive > within 3 weeks. BTW, there is nothing wrong in sending reminder for the review. It will help in prioritizing the task in the busy schedule. > > > > > > Updated release notes and removed deprecation notice. > > > Added a build fix because of removal of a macro > > RTE_FUNC_PTR_OR_ERR_RET. > > > > > > Thanks.