date:20221205

Re: [vpp-dev] bihash os_panic #vpp

2022-12-05 Thread jankincai12

Hi, I still have a doubt, why is it os_panic when the memory is not enough, 
instead of returning operation failure.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22290): https://lists.fd.io/g/vpp-dev/message/22290
Mute This Topic: https://lists.fd.io/mt/95465183/21656
Mute #vpp:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] bihash os_panic #vpp

2022-12-05 Thread jankincai12

Hi, I am using VPP bihash to implement the kernel conntrack session recording 
function, which involves frequent insertion and deletion. The memory starts to 
record from 4.xg to about 5.xg. VPP bihash os_panic, the system memory is 8g.

OS Version: Ubuntu 18.04

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22289): https://lists.fd.io/g/vpp-dev/message/22289
Mute This Topic: https://lists.fd.io/mt/95465183/21656
Mute #vpp:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] arm64 / clearfog + VPP

2022-12-05 Thread Pim van Pelt via lists.fd.io

+Josua Mayer 
Hello again Josua, you'll remember we discussed Vector Packet Processing
(VPP) on the NXP/DPAA board, and we've still been discussing this in the
community off and on. I did not manage to get VPP to run on the NXP LX2160A
Clearfog, but Xiaodong references a document from NXP that perhaps you have
contacts for? I think it would be really great to collaborate on
reproducing a running VPP on this NXP processor, and it would likely be
beneficial for your Clearfog et al product line if users knew how to run
VPP on it.

I'm willing to put in the time to make it work, but I will need to
interview/clarify a bunch of things with Solid Run and/or NXP.

groet,
Pim

On Mon, Dec 5, 2022 at 9:59 PM Xiaodong Xu  wrote:

> There is a guide to run VPP on dpaa2 board from NXP at
> https://docs.nxp.com/bundle/GUID-487B2E69-BB19-42CB-AC38-7EF18C0FE3AE/page/GUID-EBA9A5C6-2407-4AC7-87B6-C1470B2CD92D.html
>  It
> requires a few scripts as well as some driver tools (restool, etc.) not
> sure they had any specific changes to VPP for this purpose. It is unclear
> what the startup.conf looks like to run VPP either.
>
> If anyone had any successful experience to bring up VPP on a dpaa2
> platform, please share with us and it would be much appreciated.
> 
>
>

-- 
Pim van Pelt 
PBVP1-RIPE - http://www.ipng.nl/

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22288): https://lists.fd.io/g/vpp-dev/message/22288
Mute This Topic: https://lists.fd.io/mt/94234426/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] LACP issues w/ cdma/connectX 6

2022-12-05 Thread steven luong via lists.fd.io

Type
show lacp details
to see if the member interface that is not forming the bundle receives and 
sends LACP PDUs.
Type
show hardware
to see if both member interfaces have the same mac address.

From:  on behalf of Eyle Brinkhuis 
Reply-To: "vpp-dev@lists.fd.io" 
Date: Monday, December 5, 2022 at 5:23 AM
To: "Benoit Ganne (bganne)" 
Cc: vpp-dev 
Subject: [vpp-dev] LACP issues w/ cdma/connectX 6

Hi Ben,

We have a few new boxes that have a connectX 6 fitted (Mellanox ConnectX-6 Dx 
100GbE QSFP56 2-port PCIe 4 Ethernet Adapter) and we run into an issue with 
LACP (seems a popular topic these days.. :-)). We are not able to get LACP up, 
while running this:


create int rdma host-if ens3f0 name rdma0

create int rdma host-if ens3f1 name rdma1

set interface state rdma1 up

set interface state rdma0 up

create bond mode lacp

bond add BondEthernet0 rdma0

bond add BondEthernet0 rdma1

set int state BondEthernet0 up



On the switch side (Mellanox sn2700) everything is the same as with our 
Mellanox CX5 NICs (also on RDMA, with same lacp configuration as above). CX5 
stuff all works a charm.



For the CX6, we receive the BDPU’s from RDMA, and they seem to be processed:



Packet 1



00:00:52:494905: rdma-input

  rdma: rdma0 (1) next-node bond-input

00:00:52:494920: bond-input

  src b8:59:9f:67:fa:ba, dst 01:80:c2:00:00:02, rdma0 -> rdma0

00:00:52:494926: ethernet-input

  SLOW_PROTOCOLS: b8:59:9f:67:fa:ba -> 01:80:c2:00:00:02

00:00:52:494930: lacp-input

  rdma0:

Length: 110

  LACPv1

  Actor Information TLV: length 20

System b8:59:9f:67:fa:80

System priority 32768

Key 13834

Port priority 32768

Port number 25

State 0x45

  LACP_STATE_LACP_ACTIVITY (0)

  LACP_STATE_AGGREGATION (2)

  LACP_STATE_DEFAULTED (6)

  Partner Information TLV: length 20

System 00:00:00:00:00:00

System priority 0

Key 0

Port priority 0

Port number 0

State 0x7c

  LACP_STATE_AGGREGATION (2)

  LACP_STATE_SYNCHRONIZATION (3)

  LACP_STATE_COLLECTIING (4)

  LACP_STATE_DISTRIBUTING (5)

  LACP_STATE_DEFAULTED (6)

  0x:  0101 0114 8000 b859 9f67 fa80 360a 8000

  0x0010:  0019 4500  0214    

  0x0020:     7c00  0310  

  0x0030:         

  0x0040:         

  0x0050:         

  0x0060:        

00:00:52:494936: error-drop

  rx:rdma0

00:00:52:494937: drop

  lacp-input: good lacp packets — consumed



vpp# sh lacpactor state 
 partner state

interface namesw_if_index  bond interface   
exp/def/dis/col/syn/agg/tim/act  exp/def/dis/col/syn/agg/tim/act

rdma0 1BondEthernet0  0   1   0   0   1   1 
  1   10   0   0   0   0   0   0   0

  LAG ID: [(,02-fe-c6-4c-c3-62,0003,00ff,0001), 
(,00-00-00-00-00-00,0003,00ff,0001)]

  RX-state: DEFAULTED, TX-state: TRANSMIT, MUX-state: ATTACHED, PTX-state: 
PERIODIC_TX

rdma1 2BondEthernet0  0   1   0   0   0   1 
  1   10   0   0   0   0   0   0   0

  LAG ID: [(,02-fe-c6-4c-c3-62,0003,00ff,0002), 
(,00-00-00-00-00-00,0003,00ff,0002)]

  RX-state: DEFAULTED, TX-state: TRANSMIT, MUX-state: DETACHED, PTX-state: 
PERIODIC_TX



vpp# sh bond details

BondEthernet0

  mode: lacp

  load balance: l2

  number of active members: 0

  number of members: 2

rdma0

rdma1

  device instance: 0

  interface id: 0

  sw_if_index: 3

  hw_if_index: 3





vpp# sh log

2022/12/05 12:43:14:840 notice plugin/loadLoaded plugin: abf_plugin.so 
(Access Control List (ACL) Based Forwarding)

2022/12/05 12:43:14:841 notice plugin/loadLoaded plugin: acl_plugin.so 
(Access Control Lists (ACL))

2022/12/05 12:43:14:842 notice plugin/loadLoaded plugin: adl_plugin.so 
(Allow/deny list plugin)

2022/12/05 12:43:14:842 notice plugin/loadLoaded plugin: 
af_xdp_plugin.so (AF_XDP Device Plugin)

2022/12/05 12:43:14:842 notice plugin/loadLoaded plugin: 
arping_plugin.so (Arping (arping))

2022/12/05 12:43:14:843 notice plugin/loadLoaded plugin: avf_plugin.so 
(Intel Adaptive Virtual Function (AVF) Device Driver)

2022/12/05 12:43:14:843 notice plugin/loadLoaded plugin: 
builtinurl_plugin.so (vpp built-in URL support)

2022/12/05 12:43:14:843 notice plugin/loadLoaded plugin: cdp_plugin.so 
(Cisco Discovery Protocol (CDP))

2022/12/05 12:43:14:844 notice plugin/loadLoaded plugin: cnat_plugin.so 
(CNat Translate)

2022/12/05 12:43:14:860 notice plugin/loadLoaded plugin: 
crypto_ipsecmb_plugin.so (Intel IPSEC Multi-buffer Crypto Engine)

2022/12/05 12:43:14:860 notice plugin/loadLoaded plugin: 
crypto_native_plugin.so (Intel IA32 Software Crypto Engine)

2022/12/05 12:43:14:860

Re: [vpp-dev] arm64 / clearfog + VPP

2022-12-05 Thread Stanislav Zaikin

The platform looks interesting indeed, guys, please share if it's possible
to use ipsec offloading on it.

On Mon, 5 Dec 2022 at 21:59, Xiaodong Xu  wrote:

> There is a guide to run VPP on dpaa2 board from NXP at
> https://docs.nxp.com/bundle/GUID-487B2E69-BB19-42CB-AC38-7EF18C0FE3AE/page/GUID-EBA9A5C6-2407-4AC7-87B6-C1470B2CD92D.html
>  It
> requires a few scripts as well as some driver tools (restool, etc.) not
> sure they had any specific changes to VPP for this purpose. It is unclear
> what the startup.conf looks like to run VPP either.
>
> If anyone had any successful experience to bring up VPP on a dpaa2
> platform, please share with us and it would be much appreciated.
> 
>
>

-- 
Best regards
Stanislav Zaikin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22286): https://lists.fd.io/g/vpp-dev/message/22286
Mute This Topic: https://lists.fd.io/mt/94234426/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] crash in vlib_get_next_frame_internal

2022-12-05 Thread Stanislav Zaikin

Keeping you updated :)

So, having the following piece of code in src/vlib/main.c,
  /* ??? Don't need valid flag: can use frame_index == ~0 */
  if (PREDICT_FALSE (!(*nf->flags & VLIB_FRAME_IS_ALLOCATED*)))
{
  nf->frame = vlib_frame_alloc (vm, node, next_index);
  nf->flags |= VLIB_FRAME_IS_ALLOCATED;
}

  f = nf->frame;
  ...
  n_used = *f->n_vectors*; // line 371 where null dereferencing took place
I assume that I got a vlib_next_frame with flags VLIB_FRAME_IS_ALLOCATED
but without a frame inside.
The only place which does that thing was introduced by
9f5b36926b74109974e7c3ce9bb3a0a7d676c46c (which is a good job btw), so I
think we should clear that flag as it done in other places.

I prepared a fix[0], please have a look.

[0] - https://gerrit.fd.io/r/c/vpp/+/37749

On Mon, 5 Dec 2022 at 10:53, Stanislav Zaikin  wrote:

> Hello folks,
>
> I've got a crash on v22.10
> vnet[2391390]: received signal SIGSEGV, PC 0x7f4847feb994, faulting
> address 0x0
> vnet[2391390]: #0  0x7f484805e85b 0x7f484805e85b
> vnet[2391390]: #1  0x7f4847f753c0 0x7f4847f753c0
> vnet[2391390]: #2  0x7f4847feb994 vlib_get_next_frame_internal + 0x64
> vnet[2391390]: #3  0x7f484814e729 vlib_buffer_enqueue_to_next_fn_hsw +
> 0x3289
> vnet[2391390]: #4  0x7f4848dcbf2e ip4_rewrite_node_fn_hsw + 0x28ae
> vnet[2391390]: #5  0x7f4847fee6fb vlib_worker_loop + 0x1b3b
> vnet[2391390]: #6  0x7f4848040afa vlib_worker_thread_fn + 0xaa
> vnet[2391390]: #7  0x7f484803ae01 vlib_worker_thread_bootstrap_fn +
> 0x51
> vnet[2391390]: #8  0x7f4847f69609 start_thread + 0xd9
> vnet[2391390]: #9  0x7f4847ca7163 clone + 0x43
>
> (gdb) info line *0x7f4847feb994
> Line 371 of "/home/runner/work/vpp/vpp/src/vlib/main.c" starts at address
> 0x7f4847feb994  and ends at
> 0x7f4847feb998 .
>
> And the code for this line is following:
>   n_used = f->n_vectors;
>
> Which means that vlib_node_runtime_get_next_frame allocated
> vlib_next_frame with NULL in the frame field.
>
> I wonder how I can debug it further since vpp caught a segfault signal and
> in the core file I've got a completely different stacktrace. Is there a
> way to find exactly this vlib_next_frame structure? Any ideas are much
> appreciated.
>
> --
> Best regards
> Stanislav Zaikin
>


-- 
Best regards
Stanislav Zaikin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22285): https://lists.fd.io/g/vpp-dev/message/22285
Mute This Topic: https://lists.fd.io/mt/95465711/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] arm64 / clearfog + VPP

2022-12-05 Thread Xiaodong Xu

There is a guide to run VPP on dpaa2 board from NXP at 
https://docs.nxp.com/bundle/GUID-487B2E69-BB19-42CB-AC38-7EF18C0FE3AE/page/GUID-EBA9A5C6-2407-4AC7-87B6-C1470B2CD92D.html
 It requires a few scripts as well as some driver tools (restool, etc.) not 
sure they had any specific changes to VPP for this purpose. It is unclear what 
the startup.conf looks like to run VPP either.

If anyone had any successful experience to bring up VPP on a dpaa2 platform, 
please share with us and it would be much appreciated.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22284): https://lists.fd.io/g/vpp-dev/message/22284
Mute This Topic: https://lists.fd.io/mt/94234426/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] LACP issues w/ cdma/connectX 6

2022-12-05 Thread Sudhir CR via lists.fd.io

Hi Eyle,
Once we faced  LACP issue with host-if interfaces. In our topology host-if
interfaces between two containers are connected via Linux bridge.
when one container is sending LACP PDU to another container those PDU's are
dropped by Linux.  Please enable the packet trace on both sides and check
whether LACP PDU's are exchanged or not between the interfaces.

Below reference might be useful to you.

https://bugzilla.kernel.org/show_bug.cgi?id=202663

Thanks and regards,
Sudhir

On Mon, Dec 5, 2022 at 7:45 PM Eyle Brinkhuis 
wrote:

> Hi, thanks for your reply.
>
> That’s the weird thing.. we have two identical hosts connected to the same
> switch (sn2700), with same OS, same VPP version, same minx_ofed and same
> everything except for the NIC. The box with a CX5 works like a charm, the
> box with the CX6 doesn’t.. but also does, when I create the bond in
> netplan..
>
> Regards,
>
> Eyle
>
> > On 5 Dec 2022, at 15:07, najieb  wrote:
> >
> > I once experienced LACP not UP because the mode on vpp (lacp-static) did
> not match the mode on switch (lacp-dynamic). try changing the lacp mode on
> your switch.
> >
> >
>
>
> 
>
>

-- 
NOTICE TO
RECIPIENT This e-mail message and any attachments are 
confidential and may be
privileged. If you received this e-mail in error, 
any review, use,
dissemination, distribution, or copying of this e-mail is 
strictly
prohibited. Please notify us immediately of the error by return 
e-mail and
please delete this message from your system. For more 
information about Rtbrick, please visit us at www.rtbrick.com 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22283): https://lists.fd.io/g/vpp-dev/message/22283
Mute This Topic: https://lists.fd.io/mt/95468251/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] LACP issues w/ cdma/connectX 6

2022-12-05 Thread Eyle Brinkhuis

Hi, thanks for your reply.

That’s the weird thing.. we have two identical hosts connected to the same 
switch (sn2700), with same OS, same VPP version, same minx_ofed and same 
everything except for the NIC. The box with a CX5 works like a charm, the box 
with the CX6 doesn’t.. but also does, when I create the bond in netplan..

Regards,

Eyle

> On 5 Dec 2022, at 15:07, najieb  wrote:
> 
> I once experienced LACP not UP because the mode on vpp (lacp-static) did not 
> match the mode on switch (lacp-dynamic). try changing the lacp mode on your 
> switch. 
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22282): https://lists.fd.io/g/vpp-dev/message/22282
Mute This Topic: https://lists.fd.io/mt/95468251/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] LACP issues w/ cdma/connectX 6

2022-12-05 Thread najieb

I once experienced LACP not UP because the mode on vpp (lacp-static) did not 
match the mode on switch (lacp-dynamic). try changing the lacp mode on your 
switch.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22281): https://lists.fd.io/g/vpp-dev/message/22281
Mute This Topic: https://lists.fd.io/mt/95468251/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] LACP issues w/ cdma/connectX 6

2022-12-05 Thread Benoit Ganne (bganne) via lists.fd.io

I'm no expert in LACP so maybe someone can jump in to confirm whether it looks 
good on VPP side, but as we're receiving LACP packets and VPP seems to be 
happy, I wonder if the issue could be VPP failing to send LACP packets back to 
the switch? Eg. because the NIC eat them up for some reason (security...)?
Could you share the output of 'sh err' and 'sh hard', and also check whether 
the switch is receiving any LACP packets?

Best
ben

> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of Eyle
> Brinkhuis
> Sent: Monday, December 5, 2022 14:23
> To: Benoit Ganne (bganne) 
> Cc: vpp-dev 
> Subject: [vpp-dev] LACP issues w/ cdma/connectX 6
> 
> Hi Ben,
> 
> We have a few new boxes that have a connectX 6 fitted (Mellanox ConnectX-6
> Dx 100GbE QSFP56 2-port PCIe 4 Ethernet Adapter) and we run into an issue
> with LACP (seems a popular topic these days.. :-)). We are not able to get
> LACP up, while running this:
> 
> 
> 
> create int rdma host-if ens3f0 name rdma0
> 
> create int rdma host-if ens3f1 name rdma1
> 
> set interface state rdma1 up
> 
> set interface state rdma0 up
> 
> create bond mode lacp
> 
> bond add BondEthernet0 rdma0
> 
> bond add BondEthernet0 rdma1
> 
> set int state BondEthernet0 up
> 
> 
> 
> 
> On the switch side (Mellanox sn2700) everything is the same as with our
> Mellanox CX5 NICs (also on RDMA, with same lacp configuration as above).
> CX5 stuff all works a charm.
> 
> 
> 
> 
> For the CX6, we receive the BDPU’s from RDMA, and they seem to be
> processed:
> 
> 
> 
> 
> Packet 1
> 
> 
> 
> 
> 00:00:52:494905: rdma-input
> 
>   rdma: rdma0 (1) next-node bond-input
> 
> 00:00:52:494920: bond-input
> 
>   src b8:59:9f:67:fa:ba, dst 01:80:c2:00:00:02, rdma0 -> rdma0
> 
> 00:00:52:494926: ethernet-input
> 
>   SLOW_PROTOCOLS: b8:59:9f:67:fa:ba -> 01:80:c2:00:00:02
> 
> 00:00:52:494930: lacp-input
> 
>   rdma0:
> 
> Length: 110
> 
>   LACPv1
> 
>   Actor Information TLV: length 20
> 
> System b8:59:9f:67:fa:80
> 
> System priority 32768
> 
> Key 13834
> 
> Port priority 32768
> 
> Port number 25
> 
> State 0x45
> 
>   LACP_STATE_LACP_ACTIVITY (0)
> 
>   LACP_STATE_AGGREGATION (2)
> 
>   LACP_STATE_DEFAULTED (6)
> 
>   Partner Information TLV: length 20
> 
> System 00:00:00:00:00:00
> 
> System priority 0
> 
> Key 0
> 
> Port priority 0
> 
> Port number 0
> 
> State 0x7c
> 
>   LACP_STATE_AGGREGATION (2)
> 
>   LACP_STATE_SYNCHRONIZATION (3)
> 
>   LACP_STATE_COLLECTIING (4)
> 
>   LACP_STATE_DISTRIBUTING (5)
> 
>   LACP_STATE_DEFAULTED (6)
> 
>   0x:  0101 0114 8000 b859 9f67 fa80 360a 8000
> 
>   0x0010:  0019 4500  0214    
> 
>   0x0020:     7c00  0310  
> 
>   0x0030:         
> 
>   0x0040:         
> 
>   0x0050:         
> 
>   0x0060:        
> 
> 00:00:52:494936: error-drop
> 
>   rx:rdma0
> 
> 00:00:52:494937: drop
> 
>   lacp-input: good lacp packets — consumed
> 
> 
> 
> 
> vpp# sh lacpactor
> state  partner state
> 
> interface namesw_if_index  bond interface
> exp/def/dis/col/syn/agg/tim/act  exp/def/dis/col/syn/agg/tim/act
> 
> rdma0 1BondEthernet0  0   1   0   0
> 1   1   1   10   0   0   0   0   0   0   0
> 
>   LAG ID: [(,02-fe-c6-4c-c3-62,0003,00ff,0001), (,00-00-00-00-00-
> 00,0003,00ff,0001)]
> 
>   RX-state: DEFAULTED, TX-state: TRANSMIT, MUX-state: ATTACHED, PTX-state:
> PERIODIC_TX
> 
> rdma1 2BondEthernet0  0   1   0   0
> 0   1   1   10   0   0   0   0   0   0   0
> 
>   LAG ID: [(,02-fe-c6-4c-c3-62,0003,00ff,0002), (,00-00-00-00-00-
> 00,0003,00ff,0002)]
> 
>   RX-state: DEFAULTED, TX-state: TRANSMIT, MUX-state: DETACHED, PTX-state:
> PERIODIC_TX
> 
> 
> 
> 
> vpp# sh bond details
> 
> BondEthernet0
> 
>   mode: lacp
> 
>   load balance: l2
> 
>   number of active members: 0
> 
>   number of members: 2
> 
> rdma0
> 
> rdma1
> 
>   device instance: 0
> 
>   interface id: 0
> 
>   sw_if_index: 3
> 
>   hw_if_index: 3
> 
> 
> 
> 
> 
> 
> 
> vpp# sh log
> 
> 2022/12/05 12:43:14:840 notice plugin/loadLoaded plugin:
> abf_plugin.so (Access Control List (ACL) Based Forwarding)
> 
> 2022/12/05 12:43:14:841 notice plugin/loadLoaded plugin:
> acl_plugin.so (Access Control Lists (ACL))
> 
> 2022/12/05 12:43:14:842 notice plugin/loadLoaded plugin:
> adl_plugin.so (Allow/deny list plugin)
> 
> 2022/12/05 12:43:14:842 notice plugin/loadLoaded plugin:
> af_xdp_plugin.so (AF_XDP Device Plugin)
> 
> 2022/12/05 12:43:14:842 notice plugin/loadLoaded plugin:
> arping_plugin.so (Arping (arping))
> 
> 2022/12/05 12:43:14:843 notice plugin/loadLoaded plugin:
> avf_plugin.so (Intel

[vpp-dev] LACP issues w/ cdma/connectX 6

2022-12-05 Thread Eyle Brinkhuis

Hi Ben,

We have a few new boxes that have a connectX 6 fitted (Mellanox ConnectX-6 Dx 
100GbE QSFP56 2-port PCIe 4 Ethernet Adapter) and we run into an issue with 
LACP (seems a popular topic these days.. :-)). We are not able to get LACP up, 
while running this:


create int rdma host-if ens3f0 name rdma0

create int rdma host-if ens3f1 name rdma1

set interface state rdma1 up

set interface state rdma0 up

create bond mode lacp

bond add BondEthernet0 rdma0

bond add BondEthernet0 rdma1

set int state BondEthernet0 up


On the switch side (Mellanox sn2700) everything is the same as with our 
Mellanox CX5 NICs (also on RDMA, with same lacp configuration as above). CX5 
stuff all works a charm.


For the CX6, we receive the BDPU’s from RDMA, and they seem to be processed:


Packet 1


00:00:52:494905: rdma-input

  rdma: rdma0 (1) next-node bond-input

00:00:52:494920: bond-input

  src b8:59:9f:67:fa:ba, dst 01:80:c2:00:00:02, rdma0 -> rdma0

00:00:52:494926: ethernet-input

  SLOW_PROTOCOLS: b8:59:9f:67:fa:ba -> 01:80:c2:00:00:02

00:00:52:494930: lacp-input

  rdma0:

Length: 110

  LACPv1

  Actor Information TLV: length 20

System b8:59:9f:67:fa:80

System priority 32768

Key 13834

Port priority 32768

Port number 25

State 0x45

  LACP_STATE_LACP_ACTIVITY (0)

  LACP_STATE_AGGREGATION (2)

  LACP_STATE_DEFAULTED (6)

  Partner Information TLV: length 20

System 00:00:00:00:00:00

System priority 0

Key 0

Port priority 0

Port number 0

State 0x7c

  LACP_STATE_AGGREGATION (2)

  LACP_STATE_SYNCHRONIZATION (3)

  LACP_STATE_COLLECTIING (4)

  LACP_STATE_DISTRIBUTING (5)

  LACP_STATE_DEFAULTED (6)

  0x:  0101 0114 8000 b859 9f67 fa80 360a 8000

  0x0010:  0019 4500  0214    

  0x0020:     7c00  0310  

  0x0030:         

  0x0040:         

  0x0050:         

  0x0060:        

00:00:52:494936: error-drop

  rx:rdma0

00:00:52:494937: drop

  lacp-input: good lacp packets — consumed


vpp# sh lacpactor state 
 partner state

interface namesw_if_index  bond interface   
exp/def/dis/col/syn/agg/tim/act  exp/def/dis/col/syn/agg/tim/act

rdma0 1BondEthernet0  0   1   0   0   1   1 
  1   10   0   0   0   0   0   0   0

  LAG ID: [(,02-fe-c6-4c-c3-62,0003,00ff,0001), 
(,00-00-00-00-00-00,0003,00ff,0001)]

  RX-state: DEFAULTED, TX-state: TRANSMIT, MUX-state: ATTACHED, PTX-state: 
PERIODIC_TX

rdma1 2BondEthernet0  0   1   0   0   0   1 
  1   10   0   0   0   0   0   0   0

  LAG ID: [(,02-fe-c6-4c-c3-62,0003,00ff,0002), 
(,00-00-00-00-00-00,0003,00ff,0002)]

  RX-state: DEFAULTED, TX-state: TRANSMIT, MUX-state: DETACHED, PTX-state: 
PERIODIC_TX


vpp# sh bond details

BondEthernet0

  mode: lacp

  load balance: l2

  number of active members: 0

  number of members: 2

rdma0

rdma1

  device instance: 0

  interface id: 0

  sw_if_index: 3

  hw_if_index: 3



vpp# sh log

2022/12/05 12:43:14:840 notice plugin/loadLoaded plugin: abf_plugin.so 
(Access Control List (ACL) Based Forwarding)

2022/12/05 12:43:14:841 notice plugin/loadLoaded plugin: acl_plugin.so 
(Access Control Lists (ACL))

2022/12/05 12:43:14:842 notice plugin/loadLoaded plugin: adl_plugin.so 
(Allow/deny list plugin)

2022/12/05 12:43:14:842 notice plugin/loadLoaded plugin: 
af_xdp_plugin.so (AF_XDP Device Plugin)

2022/12/05 12:43:14:842 notice plugin/loadLoaded plugin: 
arping_plugin.so (Arping (arping))

2022/12/05 12:43:14:843 notice plugin/loadLoaded plugin: avf_plugin.so 
(Intel Adaptive Virtual Function (AVF) Device Driver)

2022/12/05 12:43:14:843 notice plugin/loadLoaded plugin: 
builtinurl_plugin.so (vpp built-in URL support)

2022/12/05 12:43:14:843 notice plugin/loadLoaded plugin: cdp_plugin.so 
(Cisco Discovery Protocol (CDP))

2022/12/05 12:43:14:844 notice plugin/loadLoaded plugin: cnat_plugin.so 
(CNat Translate)

2022/12/05 12:43:14:860 notice plugin/loadLoaded plugin: 
crypto_ipsecmb_plugin.so (Intel IPSEC Multi-buffer Crypto Engine)

2022/12/05 12:43:14:860 notice plugin/loadLoaded plugin: 
crypto_native_plugin.so (Intel IA32 Software Crypto Engine)

2022/12/05 12:43:14:860 notice plugin/loadLoaded plugin: 
crypto_openssl_plugin.so (OpenSSL Crypto Engine)

2022/12/05 12:43:14:861 notice plugin/loadLoaded plugin: 
crypto_sw_scheduler_plugin.so (SW Scheduler Crypto Async Engine plugin)

2022/12/05 12:43:14:861 notice plugin/loadLoaded plugin: ct6_plugin.so 
(IPv6 Connection Tracker)

2022/12/05 12:43:14:861 notice plugin/loadLoaded plugin: 
det44_plugin.so

[vpp-dev] crash in vlib_get_next_frame_internal

2022-12-05 Thread Stanislav Zaikin

Hello folks,

I've got a crash on v22.10
vnet[2391390]: received signal SIGSEGV, PC 0x7f4847feb994, faulting address
0x0
vnet[2391390]: #0  0x7f484805e85b 0x7f484805e85b
vnet[2391390]: #1  0x7f4847f753c0 0x7f4847f753c0
vnet[2391390]: #2  0x7f4847feb994 vlib_get_next_frame_internal + 0x64
vnet[2391390]: #3  0x7f484814e729 vlib_buffer_enqueue_to_next_fn_hsw +
0x3289
vnet[2391390]: #4  0x7f4848dcbf2e ip4_rewrite_node_fn_hsw + 0x28ae
vnet[2391390]: #5  0x7f4847fee6fb vlib_worker_loop + 0x1b3b
vnet[2391390]: #6  0x7f4848040afa vlib_worker_thread_fn + 0xaa
vnet[2391390]: #7  0x7f484803ae01 vlib_worker_thread_bootstrap_fn + 0x51
vnet[2391390]: #8  0x7f4847f69609 start_thread + 0xd9
vnet[2391390]: #9  0x7f4847ca7163 clone + 0x43

(gdb) info line *0x7f4847feb994
Line 371 of "/home/runner/work/vpp/vpp/src/vlib/main.c" starts at address
0x7f4847feb994  and ends at
0x7f4847feb998 .

And the code for this line is following:
  n_used = f->n_vectors;

Which means that vlib_node_runtime_get_next_frame allocated vlib_next_frame
with NULL in the frame field.

I wonder how I can debug it further since vpp caught a segfault signal and
in the core file I've got a completely different stacktrace. Is there a way
to find exactly this vlib_next_frame structure? Any ideas are much
appreciated.

-- 
Best regards
Stanislav Zaikin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22277): https://lists.fd.io/g/vpp-dev/message/22277
Mute This Topic: https://lists.fd.io/mt/95465711/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Exclude a rx-queue from RSS #dpdk #vpp #vpp_qos

2022-12-05 Thread Zhang, Fan


Hi,

vpp/flow_cli.c at master · FDio/vpp · GitHub 
 
contains some useful information to add a flow to redirect to queue X 
(check out test_flow() function's redirect_to_queue option, or 
vl_api_flow_enable_t_handler if you are using API).


After a flow is configured you may enable the flow to an interface. If 
the interface is managed by DPDK the vpp flow will be translated into 
DPDK rte_flow and configure the NIC HW. Please note not all NIC HW 
supports the flow configuration you might need.


However you still have to tweak the rest of your flows to not touch queue 0.


Regards,

Fan

On 12/5/2022 9:33 AM, ltham...@usc.edu wrote:

Hi,

I am setting num-rx-queues for a dpdk dev in vpp startup config to 4. 
This enables RSS and distribute packets coming on this interface 
between these 4 queues.


I would like to configure RTE flow and redirect certain packets to 
queue 0. When this is done, I don't want other packets to use queue 0 
due to RSS.


Is there a way to disable RSS on set of rx-queues?

-Nikhil




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22276): https://lists.fd.io/g/vpp-dev/message/22276
Mute This Topic: https://lists.fd.io/mt/95465574/21656
Mute #vpp_qos:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp_qos
Mute #dpdk:https://lists.fd.io/g/vpp-dev/mutehashtag/dpdk
Mute #vpp:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Exclude a rx-queue from RSS #dpdk #vpp #vpp_qos

2022-12-05 Thread lthammin

Hi,

I am setting num-rx-queues for a dpdk dev in vpp startup config to 4. This 
enables RSS and distribute packets coming on this interface between these 4 
queues.

I would like to configure RTE flow and redirect certain packets to queue 0. 
When this is done, I don't want other packets to use queue 0 due to RSS.

Is there a way to disable RSS on set of rx-queues?

-Nikhil

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22275): https://lists.fd.io/g/vpp-dev/message/22275
Mute This Topic: https://lists.fd.io/mt/95465574/21656
Mute #vpp_qos:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp_qos
Mute #dpdk:https://lists.fd.io/g/vpp-dev/mutehashtag/dpdk
Mute #vpp:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] bihash os_panic #vpp

Re: [vpp-dev] bihash os_panic #vpp

Re: [vpp-dev] arm64 / clearfog + VPP

Re: [vpp-dev] LACP issues w/ cdma/connectX 6

Re: [vpp-dev] arm64 / clearfog + VPP

Re: [vpp-dev] crash in vlib_get_next_frame_internal

Re: [vpp-dev] arm64 / clearfog + VPP

Re: [vpp-dev] LACP issues w/ cdma/connectX 6

Re: [vpp-dev] LACP issues w/ cdma/connectX 6

Re: [vpp-dev] LACP issues w/ cdma/connectX 6

Re: [vpp-dev] LACP issues w/ cdma/connectX 6

[vpp-dev] LACP issues w/ cdma/connectX 6

[vpp-dev] crash in vlib_get_next_frame_internal

Re: [vpp-dev] Exclude a rx-queue from RSS #dpdk #vpp #vpp_qos

[vpp-dev] Exclude a rx-queue from RSS #dpdk #vpp #vpp_qos

15 matches

Site Navigation

Mail list logo

Footer information