Re: [vpp-dev] [discuss] Question about VPP support for ARM 64

If a bug is filed, may I have the bug number, I would be love to trace this patch. BTW, how do I file a bug for VPP, I did a quick wiki search with no luck. Thanks, George -Original Message- From: Dave Barach (dbarach) [mailto:dbar...@cisco.com] Sent: Saturday, August 19, 2017 7:42 AM

Re: [vpp-dev] MLX3

We used steps below on MLX4 (25g connect4) recently to test-drive and it came up for us on RHEL. === steps: download mellanox ofed form their website, install only following packages: libmlx4*deb libmlx5*.deb libibverbs*.deb mlnx-ofed-kernel*deb mlnx-fw-updater*.deb last one will

[vpp-dev] ipsec_output.c nodes

I saw something that I have not noticed in other places and I wondered about it: /* *INDENT-OFF* */ VLIB_REGISTER_NODE (ipsec_output_node) = { .vector_size = sizeof (u32), .function = ipsec_output_node_fn, .name = "ipsec-output-ip4", }; VLIB_REGISTER_NODE (ipsec_output_node) = {

[vpp-dev] MLX3

All, Billy and I are purchasing new server(s) and it is currently being specified with Mellanox ConnectX-3. I see it is supported but how much experience do we have with this card? Do we have to use OFED etc. for perf tuning or is that only for the ConnextX-4 and 5? Thanks --Tom --

Re: [vpp-dev] [discuss] Question about VPP support for ARM 64

+1, pls add the typedef... Thanks… Dave -Original Message- From: Damjan Marion (damarion) Sent: Saturday, August 19, 2017 9:09 AM To: Dave Barach (dbarach) Cc: George Zhao ; vpp-dev@lists.fd.io; disc...@lists.fd.io; csit-...@lists.fd.io

Re: [vpp-dev] [discuss] Question about VPP support for ARM 64

GCC is able to compile ARM64 code with 256-bit vectors even if target platform have only 128-bit registers. I.e. for the u8x32 version of that function it generates: ARM64: dpdk_buffer_init_from_template(void*, void*, void*, void*, void*): ld1 {v0.16b - v1.16b}, [x4], 32

Re: [vpp-dev] Question about VPP support for ARM 64

Dear George, This specific issue isn't anywhere near as bad as you might think. As given, the code confuses 128-bit vectors with 256-bit vectors, and 64-bit vectors with 128-bit vectors. Question: does the hardware involved support 256-bit vectors? Probably not... It almost certainly does

[vpp-dev] Packet loss on use of API & cmdline

Hi, I've been doing some prototyping and load testing of the vpp dataplane, and have observed packet loss when I issue API requests or use the debug command line. Is this to be expected given the use of the worker_thread_barrier, or might there be some way I could improve matters? Currently