From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 2BC321B2C7 for ; Wed, 8 Nov 2017 15:31:46 +0100 (CET) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Nov 2017 06:31:45 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,364,1505804400"; d="scan'208";a="173228622" Received: from rnicolau-mobl.ger.corp.intel.com (HELO [10.237.221.73]) ([10.237.221.73]) by fmsmga005.fm.intel.com with ESMTP; 08 Nov 2017 06:31:44 -0800 To: Thomas Monjalon Cc: dev@dpdk.org, ferruh.yigit@intel.com, wenzhuo.lu@intel.com, konstantin.ananyev@intel.com, pablo.de.lara.guarch@intel.com References: <1510147619-8701-1-git-send-email-radu.nicolau@intel.com> <14408406.FDyP0s16KU@xps> From: Radu Nicolau Message-ID: <6923ed2c-e62e-6454-0353-44f0c2afba08@intel.com> Date: Wed, 8 Nov 2017 14:31:44 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <14408406.FDyP0s16KU@xps> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2017 14:31:47 -0000 On 11/8/2017 2:22 PM, Thomas Monjalon wrote: > Hi, > > 08/11/2017 14:26, Radu Nicolau: >> --- a/doc/guides/nics/features.rst >> +++ b/doc/guides/nics/features.rst >> @@ -900,6 +900,23 @@ Documentation describes performance values. >> See ``dpdk.org/doc/perf/*``. >> >> >> +.. _nic_features_inline_crypto_doc: > This anchor seems useless. It is, I will remove it. > >> + >> +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.