Re: [vpp-dev] Question about crypto dev queue pairs #vpp

Hi Manuel, Could you also show ipsec config on both endpoints, capture a single packet and also add trace to dpdk-crypto-input? From: vpp-dev@lists.fd.io on behalf of manuel.alo...@cavium.com Sent: Friday, February 1, 2019 10:15 AM To: vpp-dev@lists.fd.io Sub

Re: [vpp-dev] Question about crypto dev queue pairs #vpp

Hi Manuel, Did you use DPDK with the OpenSSL crypto backend? Could you provide traces of the packets on the encrypting node? Regards, Sergio From: vpp-dev@lists.fd.io on behalf of manuel.alo...@cavium.com Sent: Thursday, January 31, 2019 3:25 PM To: vpp-dev@l

Re: [vpp-dev] Question about crypto dev queue pairs #vpp

: Roberts, Lee A. Sent: Tuesday, January 29, 2019 3:49 PM To: Sergio Gonzalez Monroy; manuel.alo...@cavium.com; vpp-dev@lists.fd.io Subject: RE: [vpp-dev] Question about crypto dev queue pairs #vpp Sergio, I encountered the same problem when attempting to enable the AMD CCP poll mode driver in VPP

Re: [vpp-dev] Question about crypto dev queue pairs #vpp

Hi Manuel, This is likely a mismatch in VPP side. I only tested it with QAT (2 qps per VF) and SW cryptodevs (default 8 qps) at the time (over a year ago). I only tested it with SW cryptodevs and QAT, that was the HW I had access to. So like I mentioned before, if you do not want to rework the

Re: [vpp-dev] Question about crypto dev queue pairs #vpp

Hi Manuel, Regarding qp_id + outbound, each resource "contains" 2 queue_pairs for inbound and outbound traffic respectively. That being said, I don't see any reason why it could not be reworked to have 1 qp per resource. So regarding your first point, I reckon it is a bug given that the current

Re: [vpp-dev] segfault due to movaps unaligned access

Hi, I have to admit that the intention (when I wrote the code) of the __attribute__ ((aligned(64))) on the typedef struct was to have elements properly sized. I thought to remember that I did look at this attribute behavior before but then again my memory is not as reliable as I wish for, so no

Re: [vpp-dev] 17.10 IPsec work

Hi Matt, The idea was to use the midchain-adj infrastructure (aka new FIB, aka FIB 2.0) when using IPsec tunnel interface and build the final 'rewrite' at tunnel creation for outbound traffic. Current IPsec path for outbound packet: ... -> ip4-lookup -> ip4-rewrite ->ipsec-if-output -> esp-e

Re: [vpp-dev] Latest git vpp dpdk problem / undefined symbol: aes_gcm_enc_128_sse

Did you have any errors building the dpdk? Also could you try with nasm 2.12.02 ? Thanks, Sergio On 21/09/2017 17:07, Paweł Staszewski wrote: Operating system Ubuntu 16.10 (GNU/Linux 4.8.0-22-generic x86_64) nasm -v NASM version 2.12.01 W dniu 2017-09-21 o 17:05, Sergio Gonzalez Monroy

Re: [vpp-dev] Latest git vpp dpdk problem / undefined symbol: aes_gcm_enc_128_sse

What distro are you building on? also, what nasm version do you have installed? Thanks, Sergio On 21/09/2017 15:35, Paweł Staszewski wrote: this was installed from vpp git - then bootstraped and compiled W dniu 2017-09-21 o 09:23, Sergio Gonzalez Monroy pisze: Hi Pawel, How are you

Re: [vpp-dev] Latest git vpp dpdk problem / undefined symbol: aes_gcm_enc_128_sse

Hi Pawel, How are you installing VPP (ie. from source or using rpm/deb package)? Thanks, Sergio On 19/09/2017 19:33, Paweł Staszewski wrote: Sep 19 20:34:25 ubuntu vpp[11348]: vlib_plugin_early_init:356: plugin path /usr/lib/vpp_plugins Sep 19 20:34:25 ubuntu vpp[11348]: load_one_plugin:184: L

Re: [vpp-dev] Query for IPSec support on VPP

, why should route of Inner Source IP matter at all. It’s anyway going to be encrypted and sent across. Route of Outer IP is what shall matter, not the Inner Peer IP in tunnel mode. Thanks Mukesh On 07/09/17, 5:55 PM, "Sergio Gonzalez Monroy" wrote: Hi Mukesh, I think the

Re: [vpp-dev] Query for IPSec support on VPP

On 07/09/17, 2:12 PM, "Sergio Gonzalez Monroy" wrote: Hi Mukesh, On 07/09/2017 08:48, Mukesh Yadav (mukyadav) wrote: > HI Sergio, > > As I mentioned that transport mode is working now. > Next I tried tunnel mode. > Here I can se

Re: [vpp-dev] Query for IPSec support on VPP

workers 1 } Now since DPDK basic IPSec is working. I will try to dig in more in detail. One query I posted in early threads, possibly got missed. Currently ESP is supported, is there a plan to support AH in future? Thanks Mukesh On 0

Re: [vpp-dev] Query for IPSec support on VPP

what is configuration to test same with worker core. Will be helpful for me in future.. Thanks Mukesh On 05/09/17, 6:22 PM, "Sergio Gonzalez Monroy" wrote: Hi Mukesh, I was able to find the bug. It was not directly related to transport mode but to the setup

Re: [vpp-dev] Query for IPSec support on VPP

core, no workers). Regards, Sergio On 05/09/2017 09:28, Sergio Gonzalez Monroy wrote: On 04/09/2017 17:07, Mukesh Yadav (mukyadav) wrote: HI Sergio, I see new document as updated in latest clone is as below: dpdk { dev :81:00.0 dev :81:00.1 dev :85:01.0 dev

Re: [vpp-dev] Compile error

sion is 2.10.09. Thanks, xyxue ---- *From:* Sergio Gonzalez Monroy <mailto:sergio.gonzalez.mon...@intel.com> *Date:* 2017-09-05 16:24 *To:* 薛欣颖 <mailto:xy...@fiberhome.com>; vpp-dev <mailto:vpp-dev@

Re: [vpp-dev] Query for IPSec support on VPP

09/17, 1:52 PM, "Sergio Gonzalez Monroy" wrote: FYI I updated the doc, hopefully everything is correct and up to date now. https://gerrit.fd.io/r/#/c/8273/ Thanks, Sergio On 31/08/2017 10:00, Sergio Gonzalez Monroy wrote: > On 31/08/2017 09:37, Mu

Re: [vpp-dev] Compile error

Hi, Have you run 'make install-dep' ? Which nasm version do you have in your system? Thanks, Sergio On 04/09/2017 11:59, 薛欣颖 wrote: Hi， I got code by ： git clone https://gerrit.fd.io/r/vpp. input ‘make dpdk-install-dev’ the error infomation is shown below： Building IPSec-MB 0.46 library ma

Re: [vpp-dev] Query for IPSec support on VPP

FYI I updated the doc, hopefully everything is correct and up to date now. https://gerrit.fd.io/r/#/c/8273/ Thanks, Sergio On 31/08/2017 10:00, Sergio Gonzalez Monroy wrote: On 31/08/2017 09:37, Mukesh Yadav (mukyadav) wrote: Thanks a lot Sergio for lot of patience and help, No problem at

Re: [vpp-dev] [EXT] Re: compiling error natively on an am64 box for fd.io_vpp

com] *Sent:* 2017年8月27日3:11 *To:* Eric Chen *Cc:* Dave Barach ; Sergio Gonzalez Monroy ; vpp-dev *Subject:* Re: [vpp-dev] [EXT] Re: compiling error natively on an am64 box for fd.io_vpp Hi Eric, Same code compiles perfectly fine on ARM64 with newer gcc version. If you are starting new developmen

Re: [vpp-dev] Query for IPSec support on VPP

On 31/08/2017 09:37, Mukesh Yadav (mukyadav) wrote: Thanks a lot Sergio for lot of patience and help, No problem at all. I said before, it is great that someone else goes through the docs/wiki to double check everything is working as described. With you latest comments, I can see dpdk IPS

Re: [vpp-dev] Query for IPSec support on VPP

. Will be helpful if you can point me some sample config for DPDK IPSec or any link which shall have these pointers. Thanks Mukesh On 30/08/17, 9:14 PM, "Sergio Gonzalez Monroy" wrote: I was just reproducing your steps. Check that you have created a 'vdev crypto

Re: [vpp-dev] Query for IPSec support on VPP

ng wiki or document for making IPSec work along DPDK in VPP. Thanks Mukesh *From: *Sergio Gonzalez Monroy <mailto:sergio.gonzalez.mon...@intel.com> *Date: *Wednesday, 30 August 2017 at 2:06 PM *To: *Mukesh Yadav <mailto:mukya...@cisco.com>,

Re: [vpp-dev] Dynamically change number of cores used by VPP?

AFAIK there is no support to adjust the number of cores used or the cores frequency in runtime. Not sure if there is full support to dynamically switch between polling and interrupt mode, but I believe most of the infra is already there (read below thread). https://lists.fd.io/pipermail/vpp-dev

Re: [vpp-dev] Query for IPSec support on VPP

me out any working wiki or document for making IPSec work along DPDK in VPP. Thanks Mukesh *From: *Sergio Gonzalez Monroy *Date: *Wednesday, 30 August 2017 at 2:06 PM *To: *Mukesh Yadav , "vpp-dev@lists.fd.io" *Subject: *Re: [vpp-dev] Query for IPSec support on VPP Just for ref

Re: [vpp-dev] Query for IPSec support on VPP

Just for reference and clarity, there is no wiki entry for the DPDK crypto, only documentation page. The wiki page is for general VPP/IPSec/IKEv2. Thanks, Sergio On 30/08/2017 09:19, Sergio Gonzalez Monroy wrote: On 29/08/2017 18:25, Mukesh Yadav (mukyadav) wrote: Thanks Sergio for quick

Re: [vpp-dev] Query for IPSec support on VPP

On 29/08/2017 18:25, Mukesh Yadav (mukyadav) wrote: Thanks Sergio for quick help. Pointers cleared few of basic doubts. You are flushing out few left overs from previous releases, so thank you. I will use below wiki to proceed. https://docs.fd.io/vpp/17.10/dpdk_crypto_ipsec_doc.html Since

Re: [vpp-dev] Query for IPSec support on VPP

Hi Mukesh, On 28/08/2017 17:19, Mukesh Yadav (mukyadav) wrote: Hi, I have recently started working on VPP IPSec. My knowledge for same is limited to IPSEC. I have few queries w.r.t to broader support of IPSec in VPP. Would appreciate any pointers/help for same. As per wiki below, I have

Re: [vpp-dev] compiling error natively on an am64 box for fd.io_vpp

Hi Eric, The ipsec.api.h file should be auto generated, did you have any other error before that one? Thanks, Sergio On 25/08/2017 12:03, Eric Chen wrote: Hi I am building fd.io w/ dpdk natively on an am64 box, however encounters below error, I didn’t find ipsec.api.h under the package

Re: [vpp-dev] Issues building latest master

On Mon, Aug 14, 2017 at 4:19 AM, Sergio Gonzalez Monroy <mailto:sergio.gonzalez.mon...@intel.com>> wrote: On 14/08/2017 09:11, Marco Varlese wrote: Hi Sergio, I tried on a different machine and I got this: libdir: ${exec_prefix}/lib64 That c

Re: [vpp-dev] Issues building latest master

On 14/08/2017 09:46, Marco Varlese wrote: On Mon, 2017-08-14 at 09:37 +0100, Sergio Gonzalez Monroy wrote: On 14/08/2017 09:25, Marco Varlese wrote: On Mon, 2017-08-14 at 08:17 +0100, Sergio Gonzalez Monroy wrote: Hi, So I gather that: 1. DPDK and the SW crypto libraries are building without

Re: [vpp-dev] Issues building latest master

On 14/08/2017 09:25, Marco Varlese wrote: On Mon, 2017-08-14 at 08:17 +0100, Sergio Gonzalez Monroy wrote: Hi, So I gather that: 1. DPDK and the SW crypto libraries are building without errors 2. Only OpenSUSE displays this behavior. Only thing I can think of is that configure has different

Re: [vpp-dev] Issues building latest master

refix}/lib Thanks, Sergio Thanks, Marco Marco Varlese 08/14/17 10:04 AM >>> Sergio Gonzalez Monroy 08/14/17 9:17 AM >>> Hi, So I gather that: 1. DPDK and the SW crypto libraries are building without errors 2. Only OpenSUSE displays this behavior. Only thing I can think o

Re: [vpp-dev] Issues building latest master

On 14/08/2017 09:04, Marco Varlese wrote: Sergio Gonzalez Monroy 08/14/17 9:17 AM >>> Hi, So I gather that: 1. DPDK and the SW crypto libraries are building without errors 2. Only OpenSUSE displays this behavior. Only thing I can think of is that configure has different defau

Re: [vpp-dev] VPP compile error building vpp ipsec on Fed 26

Hi Tom, Some APIs currently used in VPP have been deprecated in OpenSSL 1.1, it would require some rework . It seems there is already a Jira ticket for it VPP-569 Thanks, Sergio On 13/08/2017 22:45, Thomas F Herbert wrote: I am getting a compile error

Re: [vpp-dev] Issues building latest master

Hi, So I gather that: 1. DPDK and the SW crypto libraries are building without errors 2. Only OpenSUSE displays this behavior. Only thing I can think of is that configure has different default libdir directory in OpenSUSE? Could you show the output of the following command: grep "libdir:" bu

Re: [vpp-dev] VPP 908 and nasm revision

Hey Tom, It wasn't so much about having a new nasm version but when we already have a newer version installed in the system, the build fails because we do not have the specific 2.12 version. Maybe a simple workaround would be to have nasm in a fedora specific _DEPENDS variable and keep the f

Re: [vpp-dev] Fortville DPDK PMD: TCP checksum offload hassles

o, Thanks for confirming that the packet_type isn’t interesting. I thought so, but... As the code stands, I wasn’t computing any TCP checksum at all. Does the i40e hardware / PMD expect tcp->checksum = ? Do other PMDs expect the same? Thanks… Dave *From:*Sergio Go

Re: [vpp-dev] Fortville DPDK PMD: TCP checksum offload hassles

On 22/06/2017 16:11, Dave Barach (dbarach) wrote: Folks, I’m having a hard time trying to convince an Intel Fortville (i40e) PMD / NIC to compute and insert TCP correct TCP checksums. In addition to the typical struct rte_mbuf setup, I add the following: if (b->flags & VLIB_BUFFER_TCP_CHE

Re: [vpp-dev] Cryptodev "issue"

Hi Marco, Wondering if you still have this issue and had time to debug it further? Regards, Sergio On 30/05/2017 08:10, Marco Varlese wrote: On Mon, 2017-05-29 at 16:20 +0100, Sergio Gonzalez Monroy wrote: On 29/05/2017 15:54, Marco Varlese wrote: On Mon, 2017-05-29 at 15:35 +0100, Sergio

Re: [vpp-dev] Cryptodev "issue"

On 29/05/2017 15:54, Marco Varlese wrote: On Mon, 2017-05-29 at 15:35 +0100, Sergio Gonzalez Monroy wrote: Hi, I have not seen that behavior before. The dpdk_crypto_sw is only for enabling SW crypto, the default is to support just HW crypto devices. I cannot think of a reason why you would

Re: [vpp-dev] Cryptodev "issue"

Hi, I have not seen that behavior before. The dpdk_crypto_sw is only for enabling SW crypto, the default is to support just HW crypto devices. I cannot think of a reason why you would see that behavior. Basically we just check if we found enough DPDK/Cryptodev HW crypto devices for the numbe

Re: [vpp-dev] DPDK Crypto Plugin: rte_cryptodev_enqueue_burst does not return Decrypted packets

Hi, So without the change to dpdk.am, does the build completes correctly (including both crypto libraries) but you fail to load the plugin? Are you building a VPP release or from master? Sergio On 22/05/2017 05:21, Avinash Gonsalves wrote: Need help with the DPDK crypto plugin, After I m

Re: [vpp-dev] The right way to disable dpdk-plugin?

On 06/04/2017 07:37, Andrew Li (zhaoxili) wrote: Hi vpp-dev, I’m trying to run VPP without dpdk enabled. According to previous mails, looks like I need to add this to startup.conf: plugins { plugin dpdk_plugin.so { disable } } However when I restart VPP, it was not happy with the fact that

Re: [vpp-dev] IPsec Multi-Tunnel performance test suite failure

? *Peter Mikus* Engineer – Software *Cisco Systems Limited* *From:*Sergio Gonzalez Monroy [mailto:sergio.gonzalez.mon...@intel.com] *Sent:* Wednesday, March 15, 2017 4:14 PM *To:* Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) ; Rybalchenko, Kirill ; Nicolau, Radu *Cc:* Tibor Frank -X

Re: [vpp-dev] IPsec Multi-Tunnel performance test suite failure

* Engineer – Software *Cisco Systems Limited* *From:*Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) *Sent:* Monday, March 13, 2017 2:19 PM *To:* 'Sergio Gonzalez Monroy' ; Maciek Konstantynowicz (mkonstan) ; Rybalchenko, Kirill ; Nicolau, Radu *Cc:* Tibor Frank -X (tifrank

Re: [vpp-dev] dpdk sw crypto- build error

1:30 AM, Sergio Gonzalez Monroy <mailto:sergio.gonzalez.mon...@intel.com>> wrote: Hi Billy, It seems that things have changed a bit since DPDK is built as a plugin and we are looking into this issue. I'll update once I have more details. Regards, Sergio

Re: [vpp-dev] dpdk sw crypto- build error

Hi Billy, It seems that things have changed a bit since DPDK is built as a plugin and we are looking into this issue. I'll update once I have more details. Regards, Sergio On 03/03/2017 16:59, Billy McFall wrote: Like the original email on this thread, I am trying to build latest vpp with v

Re: [vpp-dev] schedule vpp graph nodes on seperate cores

Hi Yusuf, Comments inline as [SGM] On 25/02/2017 15:32, yusuf khan wrote: Hi, comments inline as [YK] Br, Yusuf On Sat, Feb 25, 2017 at 12:27 AM, Kinsella, Ray mailto:ray.kinse...@intel.com>> wrote: inline On 24/02/2017 16:56, yusuf khan wrote: Hi, On my test se

[vpp-dev] VPP with DPDK Cryptodev CSIT IPsec tests

Hi, We were discussing on the CSIT project weekly call the required setup for testing VPP with DPDK Cryptodev. As it was agreed on VPP call, DPDK Cryptodev support in VPP is disabled by default and needs to be manually enabled. Basically, when we build VPP with DPDK Cryptodev support ('vpp_u