From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id E2F6C1B316 for <dev@dpdk.org>; Wed, 8 Nov 2017 16:13:33 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 238D020C7C; Wed, 8 Nov 2017 10:13:33 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 08 Nov 2017 10:13:33 -0500 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; s=mesmtp; bh=YTeFh7xcFLQGBpY+VZx4DREbT6 JrQSdgLduPf905CE0=; b=Putz0Ibaf2O+VwZbNNchBcZHIzHT9JTNRrKtmtqRGx SbZnxc9AcMdMCw9YTvXQpWomQAyf8Ki7Fwu0/+QkTTLsqr4kYnMi4V1ohQVZiX7L fBZIFZu4J+jl8MtohIg9EVqOgjZNwidRmRSnK5Urdy0XMGyzqFbwnTy/wGrY/hXN g= 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; s=fm1; bh=YTeFh7 xcFLQGBpY+VZx4DREbT6JrQSdgLduPf905CE0=; b=SDNkpVnoOrkip9czwTjCuY 0nuLRGCINDc2sweZEEY5teDm7IVB/UGeAzDdYUeiL52DGYBD561lwCSs3e63guxD AybOGM9eH8MiyNS4ydmOsNwBoqH6qqNTp9oDzBTG/C7JVsAY/pFMZ9KOFxTLA4AP EKQRr7EmHK4coz6dcmNxibHUKem1JDCtQwjQfkCg7RN695wGbQYkn5aTb8A8/KIF FuxLknrEVwHr4OsA7XmeySo5VCP7GzrTSajDj5AKs/cRAKsmAjPHFIHVI0b1Zt0J v1tXOo7OCUgdZyL9t3IUIdXAnY5YigUae3/lvYgLuUFEBNbKVHrE562/ZsgVC9yw == X-ME-Sender: <xms:HR8DWrWM_jydo3VQAYlSVFF1YS5eOaeIskomT1oRXfKP1utjN9vb_Q> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id D3CAB24735; Wed, 8 Nov 2017 10:13:32 -0500 (EST) From: Thomas Monjalon <thomas@monjalon.net> To: Radu Nicolau <radu.nicolau@intel.com> Cc: dev@dpdk.org, ferruh.yigit@intel.com, wenzhuo.lu@intel.com, konstantin.ananyev@intel.com, pablo.de.lara.guarch@intel.com Date: Wed, 08 Nov 2017 16:13:31 +0100 Message-ID: <7614729.vlcYnjIi5z@xps> In-Reply-To: <6923ed2c-e62e-6454-0353-44f0c2afba08@intel.com> 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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: added inline crypto feature X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 08 Nov 2017 15:13:34 -0000 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?