[vpp-dev] vpp 2101 , we have to reduce the frame size to 128 for our use case

Hi, We have a use case where we have to reduce the frame-size to 128, changing VLIB_FRAME_SIZE to 128 will do the trick ? or do we need to change anything else other than this ? Please advise. Thanks, Chetan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply O

[vpp-dev] Job Failures due to 'Java Connection Closed Exception'

Folks, Starting around 1:15pm DST / 5:15pm UTC, there has been a 20-30% job failure rate due to 'Java Connection Closed Exception' causing a 100% verification failure rate of VPP gerrit changes.  I have been working with Vanessa in LF-IT and Mohammed at Vexxhost to resolve the issue. Based o

[vpp-dev] VPP 21.10: 4 weeks before RC1

Hi all, It’s this time of the year again! A kind reminder that we are just under 4 weeks from the 21.10 RC1 milestone and a stable/2110 branch pull - it will happen on 22 September at noon UTC, according to the release plan at https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_21.1

Re: [vpp-dev] VPp 2101 (pcap trace)

Hi Benoit, I have tried those options but it is not working , it is only capturing the section classify filter rule that is based on dst ip address. 1) Tried with classify filter [Only dest ip with *10.20.36.168 *is coming in pcap] classify filter pcap mask l3 ip4 src match l3 ip4 src 10.20.36.1

Re: [vpp-dev] Linux CP: crash in lcp_node.c

Hoi Matt, Thanks a lot for those tips - it helped me understand the problem better. I'll answer your questions but I think the problem is a no-op, because I was using the standard 16K buffers, and they ~immedately run out with 8 threads. Raising to 128K raises total consumption to the low 30K mark

Re: [vpp-dev] master branch build failed #vpp-dev

But it is good news for pretty much everybody else involved :) Simply too old, too many missing dependencies, etc….. — Damjan > On 26.08.2021., at 14:29, jiangxiaom...@outlook.com wrote: > > it's not a good news for me > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to thi

Re: [vpp-dev] VPp 2101 (pcap trace)

Hi Ben, Thanks for your response . Let me try this and get back to you. Thanks, Chetan On Thu, Aug 26, 2021 at 5:52 PM Benoit Ganne (bganne) wrote: > > We want to capture all packets with src ip or dest ip as 10.20.30.40 .I > > have tried with classify filter but no success. Looks like I am mi

Re: [vpp-dev] master branch build failed #vpp-dev

it's not a good news for me -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20028): https://lists.fd.io/g/vpp-dev/message/20028 Mute This Topic: https://lists.fd.io/mt/85151908/21656 Mute #vpp-dev:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp-dev Gro

Re: [vpp-dev] VPp 2101 (pcap trace)

> We want to capture all packets with src ip or dest ip as 10.20.30.40 .I > have tried with classify filter but no success. Looks like I am missing > something. > Can anybody please suggest the commands . Something like this should do it: ~# vppctl classify filter pcap mask l3 ip4 src match l3 ip

Re: [vpp-dev] master branch build failed #vpp-dev

We don’t support CentOS 7 anymore… — Damjan > On 26.08.2021., at 14:01, jiangxiaom...@outlook.com wrote: > > I build vpp on centos 7 with devtoolset-9. i find the using of devtoolset-9 > was removeed in the commit, is there any purpose for it? > commit a5167edc66c639e139ffb5de4336c54bb3d8a871

Re: [vpp-dev] master branch build failed #vpp-dev

I build vpp on centos 7 with devtoolset-9. i find the using of devtoolset-9 was removeed in the commit, is there any purpose for it? > > commit a5167edc66c639e139ffb5de4336c54bb3d8a871 > Author: Damjan Marion > Date:   Fri Jul 2 16:04:26 2021 +0200 > > build: remove unused files and sections >

[vpp-dev] VPp 2101 (pcap trace)

Hi, We want to capture all packets with src ip or dest ip as 10.20.30.40 .I have tried with classify filter but no success. Looks like I am missing something. Can anybody please suggest the commands . Thanks, Chetan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. Vie

Re: [vpp-dev] master branch build failed #vpp-dev

Your C compiler is too old…. You should use gcc 8+ or clang 7+ — Damjan > On 26.08.2021., at 03:31, jiangxiaom...@outlook.com wrote: > > Hi all, > Vpp master branch build failed, anyone have the save issue > > @@@ Configuring vpp in > /home/dev/code/vpp/build-root/build-vpp_debug-native