DPDK usage discussions
 help / color / mirror / Atom feed
From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: "users@dpdk.org" <users@dpdk.org>,
	"olgas@mellanox.com" <olgas@mellanox.com>
Subject: Re: [dpdk-users] IPsec offload
Date: Wed, 8 Nov 2017 11:39:48 +0000	[thread overview]
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361013F124F@FRAEML521-MBX.china.huawei.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CC467E7@IRSMSX108.ger.corp.intel.com>

Hi Pablo
So according the crypto device matrices  here http://dpdk.org/doc/guides/cryptodevs/overview.html
For encryption HW acceleration I need to use one of these:  DPAA2 ,DPAA  or QUT  - is that correct ?
Regards
Avi
> -----Original Message-----
> From: De Lara Guarch, Pablo [mailto:pablo.de.lara.guarch@intel.com]
> Sent: Wednesday, 08 November, 2017 1:17 PM
> To: Avi Cohen (A); Thomas Monjalon
> Cc: users@dpdk.org; olgas@mellanox.com
> Subject: RE: [dpdk-users] IPsec offload
> 
> Hi Avi,
> 
> > -----Original Message-----
> > From: Avi Cohen (A) [mailto:avi.cohen@huawei.com]
> > Sent: Wednesday, November 8, 2017 10:22 AM
> > To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Thomas
> > Monjalon <thomas@monjalon.net>
> > Cc: users@dpdk.org; olgas@mellanox.com
> > Subject: RE: [dpdk-users] IPsec offload
> >
> > Pablo
> > I fixed all issues,  now the app. Is running Just  to clarify one issue:
> > I meant that my Ethernet device x540 is capable to do IPsec encryption
> > in HW.
> > What did you mean "a crypto device (SW or HW)" ?
> 
> You are talking about inline crypto there then, which I am not very familiarized.
> With crypto device, I mean a lookaside crypto device, such as QAT PMD
> (example of HW device) or AESNI MB PMD (examples of SW device).
> 
> Regards,
> Pablo
> 

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

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05  8:32 Avi Cohen (A)
2017-11-06  1:02 ` Thomas Monjalon
2017-11-06 10:25   ` Avi Cohen (A)
2017-11-06 11:13     ` Thomas Monjalon
2017-11-06 15:53       ` Avi Cohen (A)
2017-11-06 16:37         ` De Lara Guarch, Pablo
2017-11-06 16:42           ` Avi Cohen (A)
2017-11-06 16:47             ` De Lara Guarch, Pablo
2017-11-06 17:16               ` Avi Cohen (A)
2017-11-07  9:42                 ` De Lara Guarch, Pablo
2017-11-07  9:49                   ` Avi Cohen (A)
2017-11-07  9:51                     ` De Lara Guarch, Pablo
2017-11-07  8:54               ` Avi Cohen (A)
2017-11-07 11:24                 ` De Lara Guarch, Pablo
2017-11-07 13:36                   ` Avi Cohen (A)
2017-11-07 14:48                     ` De Lara Guarch, Pablo
2017-11-08  8:05                       ` Avi Cohen (A)
2017-11-08  9:20                       ` Avi Cohen (A)
2017-11-08 10:22                       ` Avi Cohen (A)
2017-11-08 11:17                         ` De Lara Guarch, Pablo
2017-11-08 11:39                           ` Avi Cohen (A) [this message]
2017-11-08 11:53                             ` De Lara Guarch, Pablo
2017-11-08 11:50       ` Avi Cohen (A)
2017-11-08 12:20         ` De Lara Guarch, Pablo
2017-11-08 12:39           ` Avi Cohen (A)
2017-11-08 13:26             ` De Lara Guarch, Pablo

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=B84047ECBD981D4B93EAE5A6245AA361013F124F@FRAEML521-MBX.china.huawei.com \
    --to=avi.cohen@huawei.com \
    --cc=olgas@mellanox.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=thomas@monjalon.net \
    --cc=users@dpdk.org \
    /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).