DPDK usage discussions
 help / color / mirror / Atom feed
From: "Stokes, Ian" <ian.stokes@intel.com>
To: Greg Rose <gvrose8192@gmail.com>,
	"Avi Cohen (A)" <avi.cohen@huawei.com>,
	 "users@dpdk.org" <users@dpdk.org>,
	"ovs-discuss@openvswitch.org" <ovs-discuss@openvswitch.org>
Subject: Re: [dpdk-users] [ovs-discuss] IPsec offload for ixgbe/i40e drivers
Date: Mon, 9 Oct 2017 10:10:16 +0000	[thread overview]
Message-ID: <CD7C01071941AC429549C17338DB8A5289171619@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1c314aa8-5727-bf9d-5c6a-9bbbb64b1146@gmail.com>

> On 10/03/2017 05:35 AM, Avi Cohen (A) wrote:
> > Hi,
> > These Intel  NIC's:  X540, 82599, I40E - supports IPsec offload But I
> > don't see that the drivers  supplied by Intel - handle it (??) Also I
> > don't see any reference in the DPDK userspace drivers
> librte_pmd_ixgbe.c ..
> > Can someone tell if this is supported somewhere ?
> > Best Regards
> > Avi
> 

Hi Avi,

The NICs do support the IPsec offload feature but currently this is not supported in DPDK.

There is ongoing work with regards the RTE_SECURITY interfaces which will be used to handle this type of offload in the DPDK community . It will not be just Intel nics supporting this feature and is expected that all nics that do support it with DPDK will use the RTE_SECURITY framework. There is an ongoing discussion on the DPDK ML with regards to its design and use below

http://dpdk.org/dev/patchwork/patch/29835/

Currently I'm also looking at implementing IPsec (non-offload, look aside only) using VPMDs and QAT devices in OVS with DPDK although this work is at early stages. It may be of use to you as I would hope to integrate it with offload functionality down the line.

If you have any feedback I would be interested to hear.

https://mail.openvswitch.org/pipermail/ovs-dev/2017-August/337919.html

Thanks
Ian
> Maybe ask the guys at Intel?
> 
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
> 
> Regards,
> 
> - Greg

> 
> > _______________________________________________
> > discuss mailing list
> > discuss@openvswitch.org
> > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
> >
> 
> _______________________________________________
> discuss mailing list
> discuss@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

  reply	other threads:[~2017-10-09 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 12:35 [dpdk-users] " Avi Cohen (A)
2017-10-05 14:59 ` [dpdk-users] [ovs-discuss] " Greg Rose
2017-10-09 10:10   ` Stokes, Ian [this message]
2017-10-15 14:37     ` Avi Cohen (A)
2017-10-15 15:41       ` Stokes, Ian

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=CD7C01071941AC429549C17338DB8A5289171619@IRSMSX101.ger.corp.intel.com \
    --to=ian.stokes@intel.com \
    --cc=avi.cohen@huawei.com \
    --cc=gvrose8192@gmail.com \
    --cc=ovs-discuss@openvswitch.org \
    --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).