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 15:22:41 +0100 Message-ID: <14408406.FDyP0s16KU@xps> References: <1510147619-8701-1-git-send-email-radu.nicolau@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 5EBAB1B282 for ; Wed, 8 Nov 2017 15:22:43 +0100 (CET) In-Reply-To: <1510147619-8701-1-git-send-email-radu.nicolau@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" 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. > + > +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?