DPDK patches and discussions
 help / color / mirror / Atom feed
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
Subject: Re: [dpdk-dev] [PATCH] doc: added inline crypto feature
Date: Wed, 08 Nov 2017 16:13:31 +0100	[thread overview]
Message-ID: <7614729.vlcYnjIi5z@xps> (raw)
In-Reply-To: <6923ed2c-e62e-6454-0353-44f0c2afba08@intel.com>

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?

  reply	other threads:[~2017-11-08 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 13:26 Radu Nicolau
2017-11-08 14:22 ` Thomas Monjalon
2017-11-08 14:31   ` Radu Nicolau
2017-11-08 15:13     ` Thomas Monjalon [this message]
2017-11-08 15:40       ` Radu Nicolau
2017-11-09 12:23 ` [dpdk-dev] [PATCH v2] " Radu Nicolau
2017-11-09 12:29   ` [dpdk-dev] [PATCH v3] " Radu Nicolau
2017-11-12  3:33     ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7614729.vlcYnjIi5z@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=radu.nicolau@intel.com \
    --cc=wenzhuo.lu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).