This issue, we have seen on centos as well. Just for work around,
ip link set promisc on eth0 #[eth0 --- PF interface]
ip link set eth00 vf 0 spoofchk off #[give your vf id ]
ip link set eth0 vf 0 trust on,
, But you will see other packet on vpp VF interface as we
The new vpp cli to show ip4-arp and ip6-neighbor entries is “show ip neighbors”:
DBGvpp# sho ip neighbor
Time IPFlags Ethernet
Interface
8.436410.0.3.3 D00:50:56:88:00:ac
GigabitEthernet1b
Hi!
I was doing some initial experimentation with VPP/SRIOV/DPDK and I just
wanted to see if some of the things I was experiencing we're expected. I
was looking at understanding the baseline behavior for something like VPP +
DPDK.
I have a small test POC with the following topology.
VM Ubuntu 18
Packet size is 64B.
From: Mrityunjay Kumar
Sent: Thursday, May 14, 2020 2:18 PM
To: Christian Hopps
Cc: Govindarajan Mohandoss ; s...@tkos.co.il;
vpp-dev@lists.fd.io; Nitin Saxena ; nd
Subject: Re: [vpp-dev] Performance on the Macchiatobin
> We measured IPv4 forwarding performance in the
> On 14 May 2020, at 18:43, Mrityunjay Kumar wrote:
>
> Hi Team
> Please correct me if I understood wrongly.
> I believe, socket-mem inside dpdk { .. } section has been deprecated. Now in
> latest VPP release , there is no option to specifying socket-mem manually.
it is removed to avoid confu
> We measured IPv4 forwarding performance in the beginning of 2019 (with
VPP Master branch) and got 5.77 MPPS with single core @ 1.6 GHz
---
Friends, what was the packet size with this MPPS. Good if you share some
more details.
*Regards*,
Mrityunjay Kumar.
Mobile: +91 - 9731528504
On Fri, Ma
Hi Govindarajan,
Thanks for your response.
I have just tried a similar test on my board (restricted to 1.6GHz),
with VPP 19.01 and the marvell mvpp2 plugin and got 5.4Mpps (2.7Mpps RX
from each port) with two cores (one for each port, one RXQ).
I am getting the same results from the DPDK driver,
We've also seen good numbers from these boxes; however, we have had issues with
connecting them back-to-back (they don't work that way the interfaces flap),
they seem to work when connected through a *non-marvel* based switch. IOW
there's something weird going on with the marvel chip talking to
Hi Shmuel,
We measured IPv4 forwarding performance in the beginning of 2019 (with VPP
Master branch) and got 5.77 MPPS with single core @ 1.6 GHz. We used Marvell
I/O Plugin (PMD) and not DPDK. We don’t have the latest performance numbers.
Currently, our Macchiatobin boards are not functional
Hi Team
Please correct me if I understood wrongly.
I believe, socket-mem inside dpdk { .. } section has been deprecated. Now
in latest VPP release , there is no option to specifying socket-mem
manually. VPP has taken forcefully ownership on platform and allocating
memory from both NUMA socket.
-
Hi vpp-devers,
We have a report of an unexpected behavior when using a static NAT with
ICMP.
It appears that configuring an outside interface to allow ICMP also allows
forwarding
of all protocols as well.
If you start with, say, a blocked TCP on port 22 and an SNMP on port 161,
then
adding a NAT
Excellent!
Thanks getting RC1 completed in a timely fashion -- well done.
-daw-
On 5/13/2020 7:04 PM, Andrew Yourtchenko wrote:
Hi all,
This is to announce that the VPP 20.05 RC1 milestone is complete!
The newly created stable/2005 branch is ready for your fixes in
preparation for the RC2 mil
Well would be a nice tool if one could use it while developing with changes to
the API, but the changed API issue (an added function, which *should* be
backward compatible) and go packaging nightmare with trying to regenerate the
vpp API inside dependent packages (vpp-agent which then breaks cn-
Hi,
I have noticed that there has been some work on the Macchiatobin on vpp
(as a part of the aarach64 project).
However, I have not managed to find any performance results for the
Macchiatobin as it is not a part of CSIT.
I have found this related(?) [1] JIRA task from 2019/2018, but with no
ac
Sorry for polluting this thread. I just noticed (too late) that Chris
started a new thread with a different subject to address Govind's issue.
Thanks,
-Matt
On Thu, May 14, 2020 at 9:38 AM Matthew Smith via lists.fd.io wrote:
>
> Hi Govind,
>
> I recently started seeing errors similar to the o
Hi Govind,
I recently started seeing errors similar to the one you reported when
running git review on CentOS 7. I updated to a newer version of git review
and that fixed the issue.
Older versions of git review use a branch format that is deprecated in
gerrit. I think it changed at some point fro
Hi Neale,
So I've since tried out setting SPD on the interface with the IPv6 address,
and even though I am not able to ping the interface, I see that it does
receive and process packets (which I had erroneously assumed it did not
when it became unpingable).
I added a new SPD and added a policy l
API stability is borderline critical for a project like VPP I think. Yes, it
can be used stand-alone, but real value is added by building products on top of
it.
Also important is having an API framework that allows for backward-compatible
changes to the API for making improvements.
I'm not sur
Andrew and I have discussed a process around API changes with the goal to limit
the impact on VPP consumers.
One big painpoint in tracking VPP releases for users of the VPP binary has been
API changes.
We want to ensure:
- A production API never changes.
- A production API can be deprecated wit
Has anyone ever tried to build this with a development version (where APIs have
changed)?
After some go fmt.Printf debugging I see that I have 3 incompatible API calls
with vpp1908 (.01) binapi. It's really not obvious since i'm not a go packaging
expert how to update everything. I did find som
FWIW, I had documented (mostly for myself) the process I used from a while ago:
http://stdio.be/blog/2017-06-06-Creating-drafts-and-changes-for-VPP/
It’s a bit more typing, but works well over HTTPS (IIRC git-review was very
insistent on SSH to gerrit port.. it does ask for the password - which
Hi folks,
I've ran into the same issue when trying to submit a CSIT patch after upgrading
my Debian distro (which also updated git review). It turns out that my git
review (version 1.25.0) is using improper default gerrit namespace. From git
review 1.27.0 release notes [0]:
Update defau
Yes, looking at that now. Should have googled first :)
I think the only thing missing here is the usage bar to present "idleness"
per-worker/core. But this is a great start.
Thanks,
Chris.
> On May 14, 2020, at 5:25 AM, Benoit Ganne (bganne) via lists.fd.io
> wrote:
>
> Hi Chris,
>
>> Has a
Hi Chris,
> Has anyone contemplated the possibility of a "vpptop" like utility for
> VPP? The thought crossed my mind while I was using htop to help debug some
> performance problems I've been having that aren't directly related to vpp
> processing.
Something like this https://github.com/Pantheon
https://github.com/PantheonTechnologies/vpptop may be of interest to you
De : au nom de Christian Hopps
Date : jeudi 14 mai 2020 à 11:19
À : vpp-dev
Cc : Christian Hopps
Objet : [vpp-dev] blinkenlights .. vpptop?
Has anyone contemplated the possibility of a "vpptop" like utility for VPP? The
Has anyone contemplated the possibility of a "vpptop" like utility for VPP? The
thought crossed my mind while I was using htop to help debug some performance
problems I've been having that aren't directly related to vpp processing.
I'm thinking that vpptop could present a dashboard like top does
26 matches
Mail list logo
