From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 1C5A52C4F for ; Mon, 7 Aug 2017 19:41:58 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B40FA218E9; Mon, 7 Aug 2017 13:41:57 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 07 Aug 2017 13:41:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=GbLao04JX4oRS3t /0spXNeYOjyCCF6XHhIt/VvBvZlk=; b=A8UdrfZ+dL0WRqGxzOMYDRdJb4wIjlC BlMdcOnifBp5ChvPwupyRJ0GKgNQ7x8wOCaOhkvj2ffHELblnmvyVcOdMmKiNSNx ULqevLub0AseblzyGPsnCjARhpbOPJRqWF8qvg0WSIzpUFV4+0gIzKB9tjkREWTg eokj0CnW7ql0= 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-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=GbLao04JX4oRS3t/0spXNeYOjyCCF6XHhIt/VvBvZlk=; b=e+xcSg0k 0iD0kv9HcBBq489LJwKWy1m0hb4oIIUZx7vEh881+C1nZI0Q5B06gvUwzigufeEq UzGvW7XohfvQ+8D/fezd3OqmmmMZkqBmv6TVMjBSoEI7YWM2BtqxyrV5YsSc9a/T ZZdW8gcSxc4kRIi5FRE4/7snV0qP3br2MHEX30GQ9yR9lWrwQ6+ohv+M3SOYUqD4 DuGsNk4KnW5LwgzHdvw+j3nLnzBYHssu04bPgcwVt6gAlGf1rqcy4LrstYz7Eyct i5DYoP8UfsY8iGQeLZo7xf7kAMKFypsuZ+ftSoJe8EYpYRjMcfrT/EG+U/R5a3+w FbFetHew0EOmwQ== X-ME-Sender: X-Sasl-enc: 9wEv0cxkyjA+YOltGJILhQ8lcu+amesxpniWFAMpKjve 1502127717 Received: from xps.localnet (eth-west-pareq2-46-193-0-155.wb.wifirst.net [46.193.0.155]) by mail.messagingengine.com (Postfix) with ESMTPA id 40A9B2479F; Mon, 7 Aug 2017 13:41:57 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: Hemant Agrawal , Akhil Goyal , declan.doherty@intel.com, radu.nicolau@intel.com, aviadye@mellanox.com, borisp@mellanox.com, pablo.de.lara.guarch@intel.com Date: Mon, 07 Aug 2017 19:41:55 +0200 Message-ID: <2679300.3rDZ1MV7ox@xps> In-Reply-To: References: <20170803153211.23073-1-akhil.goyal@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: announce ABI change for cryptodev and ethdev 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: , X-List-Received-Date: Mon, 07 Aug 2017 17:41:58 -0000 04/08/2017 07:26, Hemant Agrawal: > On 8/3/2017 9:02 PM, Akhil Goyal wrote: > > Support for security operations is planned to be added > > in ethdev and cryptodev for the 17.11 release. > > > > For this following changes are required. > > - rte_cryptodev and rte_eth_dev structures need to be added > > new parameter rte_security_ops which extend support for > > security ops to the corresponding driver. > > - rte_cryptodev_info and rte_ethd_dev_info need to be added > > with rte_security_capabilities to identify the capabilities of > > the corresponding driver. It is not explained what is the fundamental difference between rte_security and rte_crypto? It looks to be just a technical workaround. Why the ABI would be changed by rte_security additions? > > Signed-off-by: Akhil Goyal > > > Acked-by: Hemant Agrawal No more opinions outside of NXP? It seems there is not yet a consensus on how to manage IPsec offloading. I heard there were some phone calls about these stuff but nothing clear appears publicly on the mailing list. Looks to be a community failure.