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
: 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
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
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
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 ->
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
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:
, 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"
<sergio.gonzalez.mon...@intel.com> wrote:
On 07/09/17, 2:12 PM, "Sergio Gonzalez Monroy"
<sergio.gonzalez.mon...@intel.com> 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
ukesh
On 05/09/17, 7:49 PM, "Sergio Gonzalez Monroy" <sergio.gonzalez.mon...@intel.com> wrote:
There are a few different ways to set cores/workers, best explained in
the following link:
https://wiki.fd.io/view/VPP/Usi
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"
<sergio.gonzalez.mon...@intel.com> wrote:
Hi Mukesh,
I was able to find the bug. It was not directly rela
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
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
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
:* 2017年8月27日3:11
*To:* Eric Chen <eri...@marvell.com>
*Cc:* Dave Barach <dbar...@cisco.com>; Sergio Gonzalez Monroy
<sergio.gonzalez.mon...@intel.com>; vpp-dev <vpp-dev@lists.fd.io>
*Subject:* Re: [vpp-dev] [EXT] Re: compiling error natively on an am64
box for fd.io_vpp
Hi E
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
.
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"
<sergio.gonzalez.mon...@intel.com> wrote:
I was just reproducing your steps.
Che
eems still config is missing something.
Can you point me out any working wiki or document for making IPSec
work along DPDK in VPP.
Thanks
Mukesh
*From: *Sergio Gonzalez Monroy <sergio.gonzalez.mon...@intel.com>
<mailto:sergio.gonzalez.mon...@intel.com>
*Dat
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).
me out any working wiki or document for making IPSec
work along DPDK in VPP.
Thanks
Mukesh
*From: *Sergio Gonzalez Monroy <sergio.gonzalez.mon...@intel.com>
*Date: *Wednesday, 30 August 2017 at 2:06 PM
*To: *Mukesh Yadav <mukya...@cisco.com>, "vpp-dev@lists.fd.io"
on, Aug 14, 2017 at 4:19 AM, Sergio Gonzalez Monroy
<sergio.gonzalez.mon...@intel.com
<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
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
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
}/lib
Thanks,
Sergio
Thanks,
Marco
Marco Varlese 08/14/17 10:04 AM >>>
Sergio Gonzalez Monroy <sergio.gonzalez.mon...@intel.com> 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
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:"
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
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
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
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
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
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
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
?
*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)
<pmi...@cisco.com>; Rybalchenko, Kirill
<kirill
Gonzalez Monroy
<sergio.gonzalez.mon...@intel.com
<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.
34 matches
Mail list logo
