DPDK patches and discussions
 help / color / mirror / Atom feed
From: Declan Doherty <declan.doherty@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	bruce.richardson@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: claim responsability for various sample apps
Date: Fri, 27 Nov 2015 14:58:06 +0000	[thread overview]
Message-ID: <56586F7E.5000208@intel.com> (raw)
In-Reply-To: <1570932.NB3qutnkrq@xps13>

On 27/11/15 14:31, Thomas Monjalon wrote:
> 2015-11-27 14:14, Pablo de Lara:
>> Co-maintain helloworld, l2fwd and dpdk-qat sample apps.
>
> Naive question: what is the benefit of dpdk-qat compared to l2fwd-crypto?
> Is it something we can drop?
>

So the dpdk-qat sample application is a sample of how to use the QAT 
library APIs from a DPDK application allowing the user to schedule work 
with the QAT kernel devices. The QAT API has support for a number of QAT 
devices (both the cave-creek and coleto-creek family of devices) which 
support symmetric crypto, asymmetric crypto and compression operations.

The l2fwd application demonstrates using the new DPDK symmetric crypto 
APIs in packet processing work flow, with the crypto processing 
implemented by DPDK userspace PMDs, this currently includes support for 
both the AES-NI multi-buffer PMD as well as the QAT PMD.

Declan

  reply	other threads:[~2015-11-27 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 14:14 Pablo de Lara
2015-11-27 14:31 ` Thomas Monjalon
2015-11-27 14:58   ` Declan Doherty [this message]
2015-11-27 14:31 ` Bruce Richardson
2015-12-06 16:46   ` 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=56586F7E.5000208@intel.com \
    --to=declan.doherty@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=thomas.monjalon@6wind.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).