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 1C9E5A04FA; Wed, 5 Feb 2020 16:22:01 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id ECD6E1C2A2; Wed, 5 Feb 2020 16:22:00 +0100 (CET) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by dpdk.org (Postfix) with ESMTP id 5728F1C24B for ; Wed, 5 Feb 2020 16:22:00 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id A87276CDB; Wed, 5 Feb 2020 10:21:59 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 05 Feb 2020 10:21:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=QaaTXBZDPA8mfC3s8xo8PiHLab0mV75HZqbraQ+3RhQ=; b=kynqPAXeuJd7 nBK3tHth/SrePfBwrj38l4pF/9SJgqLtSQXI6YP5g63a9OPBjqMHEhhYLCdjkzB2 aVxQZWpq0nFsHkB8NYsDNbTRIN4Qo0hOzPjUMxHauJAVfhRCJ0CmSSf7C37Nf8Jr /fIwareBUFcYkXlKGqvYFnxkxw/vvGo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=QaaTXBZDPA8mfC3s8xo8PiHLab0mV75HZqbraQ+3R hQ=; b=TR09wS4L12YlWzX3igvE8AZ0jDT1r5Qjkcc89SksdtUQ6CNDCf8wQuJX6 UH1qovr10hhQSMWdyf7EOkMSpnYK4hlzzHTBEPq9yZhP05qc7BPRQ1Ag2CMwEc5z 5LfuK0xWDUP9JNh2yhjRxmV9mHftHFmWGoSh0tMroJTY3Ifv5CopX1GgbFbLtMpT lsAgS83njuoXxtUpx/v4FmCoxgQjIF2xe2zA+7R61cE4eYmeDQ+PhV0/RexMHYSN Vb/WcYZYr+Z1vlgFl4rOeSs9a6xhGWV6BqXJmC5WQ8OXeanybsyklYL/N8S77L2v YwDvW/gPvvy2/wvL7rRLe5wAkJgxg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrhedugdejgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucffoh hmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvddtfedrudekgeenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrsh esmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 937E83280065; Wed, 5 Feb 2020 10:21:57 -0500 (EST) From: Thomas Monjalon To: "Trahe, Fiona" Cc: Anoob Joseph , "Kusztal, ArkadiuszX" , Akhil Goyal , "dev@dpdk.org" , Narayana Prasad Raju Athreya , Tejasree Kondoj , Jerin Jacob Kollanukkaran , "bluca@debian.org" , "ktraynor@redhat.com" , "david.marchand@redhat.com" , "nhorman@tuxdriver.com" , "Kinsella, Ray" , "Yigit, Ferruh" , "Richardson, Bruce" Date: Wed, 05 Feb 2020 16:21:56 +0100 Message-ID: <2478884.q0ZmV6gNhb@xps> In-Reply-To: References: <20200113104347.7308-1-arkadiuszx.kusztal@intel.com> <2631430.Y6S9NjorxK@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3] cryptodev: add chacha20-poly1305 aead algorithm 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" 05/02/2020 15:41, Trahe, Fiona: > From: Thomas Monjalon > > 15/01/2020 16:53, Akhil Goyal: > > > > > This patch adds Chacha20-Poly1305 AEAD algorithm to Cryptodev. > > > > > > > > > > Signed-off-by: Arek Kusztal > > > > > Acked-by: Fiona Trahe > > > > > > > > Acked-by: Anoob Joseph > > > > > > > Acked-by: Akhil Goyal > > > > > > Applied to dpdk-next-crypto > > > > As discussed in other email threads, > > this patch was causing an ABI breakage and had to be reverted: > > http://git.dpdk.org/dpdk/commit/?id=f5862ae99 > > Sorry, this feature will miss 20.02 release I'm afraid. > > > > 2 actions should be taken: > > - try to re-intoduce the feature with function versioning > > - improve ABI stability in DPDK 20.11 for future features > > [Fiona] Agreed, it's underway. Any estimation of time? I expect a lot of discussions on the solution, especially because it is a primer. > The QAT ChaChaPoly patchset including the unit tests will also need to be reverted. > https://patches.dpdk.org/patch/64729/ > https://patches.dpdk.org/patch/64730/ Yes, this is what I did in one commit.