Hi Hemant,
Yes, VPP is tested with Arm patforms. Arm machines are in VPP lab and
are part of CI/CSIT. Every patch submitted undergoes testing on Arm platforms.
The Marvell plugin is similar to the native drivers. Hence the performance is
better when compared to DPDK plugin.
Thanks,
Honn
If one notices that rest of the code at the link below uses "hash_table",
and only the line of code shown below uses "hash". This is why I sent out
my email.
Hemant
From: vpp-dev@lists.fd.io On Behalf Of hemant via
lists.fd.io
Sent: Tuesday, November 24, 2020 6:02 PM
To: vpp-dev@lists.fd.
Hi Paul,
> No.
>
> crc is actually a misnomer here. If you say crc, one assumes binascii.crc32.
> That is not what crc is. What is exposed as .crc is actually a custom
> function in vppapigen called foldup_blocks, which is dependent on the version
> of vppapigen that generated it.[0]. (Ask
/resource/libraries/python/VPPUtil.py appears responsible:
@staticmethod
def vpp_enable_elog_traces(node):
"""Enable API/CLI/Barrier traces on the specified topology node.
:param node: Topology node.
:type node: dict
"""
PapiSocketExecuto
Artem,
2.5.
Make existing code support configurable UDP port.
Either per system (if so put it in the _main_t structure. Or per tunnel
(vxlan_gbp_tunnel_t) or per makes sense.
Best regards,
Ole
> On 25 Nov 2020, at 20:45, Artem Glazychev wrote:
>
> Hi everyone,
>
> I want to discuss the enh
Honnappa,
Got it, thanks. I am new to VPP and wondering about the path to the DPDK
plugin? Has Arm been also tested with VPP since I hear from you only about Arm
and DPDK. I also noticed in the vpp/src/plugins/marvell notes that the plugin
works 30% faster if DPDK is disabled.
Thanks,
Heman
Hi everyone,
I want to discuss the enhancement of VxLAN.
As we know VxLAN supports only 4789 udp-port (IANA standard).
What if we expand on the current implementation and let the user choose the
port he wants to?
I have some thoughts on this.
*1.* Add an additional nodes in existing feature if
No.
crc is actually a misnomer here. If you say crc, one
assumes binascii.crc32. That is not what crc is. What is exposed as .crc
is actually a custom function in vppapigen called foldup_blocks, which is
dependent on the version of vppapigen that generated it.[0]. (Ask me how I
know...) In fact
A naive implementation of that will break all of the CRC for the affected
messages, which effectively means abandoning the message stability process.
--a
> On 25 Nov 2020, at 17:27, Paul Vinciguerra wrote:
>
>
> I would like to socialize the idea of removing the backwards_compatible
> optio
I would like to socialize the idea of removing the backwards_compatible
option from the .api files before the upcoming and any future releases.
The commit message states:
This allows adding backwards compatible (as guaranteed by the developer)
enums.
The enums marked backwards compatible are not
On 25.11.2020., at 16:55, Juraj Linkeš
mailto:juraj.lin...@pantheon.tech>> wrote:
Hi Damjan, Benoit,
In the CSIT call I've learned that you were looking into why VPP Device jobs
sometimes fail. I'm working on adding VPP Device jobs for arm and we're seeing
the same issue that's behind these r
Hi Damjan, Benoit,
In the CSIT call I've learned that you were looking into why VPP Device jobs
sometimes fail. I'm working on adding VPP Device jobs for arm and we're seeing
the same issue that's behind these random failures, possibly even more
frequently.
There are two high level observation
Hi Elias,
This is correct.
The patch you mentioned did improve logging: previously those error messages
were silently discarded.
Here is what happened: support for multiple mac filtering per interface was
added a few weeks back. To support that, when you add a bond with lacp, it is
now trying t
Hello VPP experts,
Using the current master branch, we now get log messages like this
(shown by journalctl in red color):
Nov 25 15:10:29 vnet[...]: interface: hw_add_del_mac_address:
vnet_hw_interface_add_del_mac_address: Secondary MAC Addresses not
supported for interface index 0
Nov 25 15:10:2
Thank you Florin!
On Tue, Nov 24, 2020 at 8:54 PM Florin Coras wrote:
> Hi Bill,
>
> Ah, you must manually enable “life cycle” events since those are
> responsible for track initialization, i.e., tcp debug group 0 level 1. To
> avoid the hassle, here’s a patch [1] that enables them whenever even
15 matches
Mail list logo
