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 42F2EA04FA; Wed, 5 Feb 2020 15:29:04 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5CD701C1D0; Wed, 5 Feb 2020 15:29:03 +0100 (CET) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) by dpdk.org (Postfix) with ESMTP id 7C2831C1AC for ; Wed, 5 Feb 2020 15:29:01 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id D7A898AB4; Wed, 5 Feb 2020 09:28:59 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 05 Feb 2020 09:28: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=36/D6yUapeLWlTgmbbjcK1YYQfI+pSHNNPofzL8nL9Q=; b=Cvgtuxenq+aQ Yfmf8TS8t25fm34UpaNslZvHR1HCxV77QuEhecgncGQcSnnNysOhAizjAFEpbJQt pXneXRjFKYNuUW++reWYQLfcgG1pUMJUA1qXAxdkFhwN0BLu784SOEZHzXSuOUAm m2zLs8YyJkId46GlcL/UKb0EOABW9MA= 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=36/D6yUapeLWlTgmbbjcK1YYQfI+pSHNNPofzL8nL 9Q=; b=Gul5e86mdNL8Uu6+cpkW4KRzlBGIJiZdgS+D1FHtIDKS4Zl/L+kboyO8X Ce9Uv08VUn/1dtyn7B1Hl3PckbdFWoUl+TZbcx0VcjVhqlkinRHfW/LcraXpcKlE xG9ZDLBz24rAY2tGP2Gp3d1NwL+Kbj38MjlUaRV7zr1lmYdURfmgg911lgbiBclZ 9hrIu+ZtXsT+SoqfSAmaWH66P2B9CYyHw8mtczmETvoB2Bv/11DLj+p89CbuFPAd 0I8VVhjcEtO1h4LDpYjtiIixEJ6Y/azpXmiWvf81hEUoXZhGTyndAXMNvHEhtCs1 Fumyd7rwR3wdRvwG1A1CIy8jYPBdA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrhedugdeifecutefuodetggdotefrodftvf 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 92930328005D; Wed, 5 Feb 2020 09:28:57 -0500 (EST) From: Thomas Monjalon To: Anoob Joseph , Arek Kusztal , "fiona.trahe@intel.com" , Akhil Goyal Cc: "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, ray.kinsella@intel.com, ferruh.yigit@intel.com, bruce.richardson@intel.com Date: Wed, 05 Feb 2020 15:28:56 +0100 Message-ID: <2631430.Y6S9NjorxK@xps> In-Reply-To: References: <20200113104347.7308-1-arkadiuszx.kusztal@intel.com> 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" 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 We are all (hardly) learning how to maintain ABI compatibility, as this is our first real issue since the new ABI policy. Thanks for understanding.