DPDK usage discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Avi Cohen (A)" <avi.cohen@huawei.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 12:20:45 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC46989@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <B84047ECBD981D4B93EAE5A6245AA361013F1260@FRAEML521-MBX.china.huawei.com>

Hi Avid,

> -----Original Message-----
> From: Avi Cohen (A) [mailto:avi.cohen@huawei.com]
> Sent: Wednesday, November 8, 2017 11:50 AM
> To: Thomas Monjalon <thomas@monjalon.net>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Cc: users@dpdk.org; olgas@mellanox.com
> Subject: RE: [dpdk-users] IPsec offload
> 
> Hi Thomas
> 
> 
> > 06/11/2017 11:25, Avi Cohen (A):
> > > Thank you Thomas
> > > Is this was tested on a specific HW e.g.  Mellanox Innova  / other ?
> >
> > Mellanox hardware will probably be supported in 18.02.
> > There are some experimental support for NXP DPAA2 and Intel ixgbe in
> > DPDK 17.11.
> [Avi Cohen (A)]
> The Intel x540-AT2 is using the ixgbe driver According to
> http://dpdk.org/doc/guides/cryptodevs/qat.html
> The QAT crypto driver which spports encryption in HW  supports the
> following Intel devices:
> - Intel QuickAssist Technology DH895xCC
> - Intel QuickAssist Technology C62x
> - Intel QuickAssist Technology C3xxx
> - Intel QuickAssist Technology D15xx
> 
> Do you know if the x540-AT2 NIC is also supported ?

Even though Thomas is the DPDK main tree maintainer and that has a vast knowledge of it :),
Don't expect him to know about what an Intel NIC supports.

You are looking at two different things here. QAT driver works on the QAT devices mentioned above.
But you are looking for inline crypto capability in NIC devices, there is no reference in our documentation yet.
We will add that shortly.

Thanks,
Pablo

> Regards,
> Avi
> 

  reply	other threads:[~2017-11-08 12:20 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)
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 [this message]
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=E115CCD9D858EF4F90C690B0DCB4D8976CC46989@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=avi.cohen@huawei.com \
    --cc=olgas@mellanox.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).