From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] doc: added inline crypto feature Date: Wed, 08 Nov 2017 16:13:31 +0100 Message-ID: <7614729.vlcYnjIi5z@xps> References: <1510147619-8701-1-git-send-email-radu.nicolau@intel.com> <14408406.FDyP0s16KU@xps> <6923ed2c-e62e-6454-0353-44f0c2afba08@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, ferruh.yigit@intel.com, wenzhuo.lu@intel.com, konstantin.ananyev@intel.com, pablo.de.lara.guarch@intel.com To: Radu Nicolau Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id E2F6C1B316 for ; Wed, 8 Nov 2017 16:13:33 +0100 (CET) In-Reply-To: <6923ed2c-e62e-6454-0353-44f0c2afba08@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 08/11/2017 15:31, Radu Nicolau: > On 11/8/2017 2:22 PM, Thomas Monjalon wrote: > > 08/11/2017 14:26, Radu Nicolau: > >> + > >> +Inline crypto > >> +------------- > >> + > >> +Supports inline crypto processing (eg. inline IPsec). See Security library for more details. > > > > As there are several types of inline crypto, don't you think it deserves > > several separate features? > > We don't differentiate in the offload, net, mbuf APIs; it's all > "security offload". > rte_security is the one that deals with different kinds of inline > crypto, but in the NIC section it's all the same. OK How can we document which kind of inline crypto is supported with which device?