Hi ,
Have one basic doubt on applicability of VppCom library for a use case that we
have as below.
Use Case with following requirements:
1. control plane app needs to communicate with different VPP worker threads
2. control plane app may need to send messages to vpp workers with message size
th
> Please don’t link vpp_api_test against libvnet.so. Your test plugin – and
> vpp_api_test by implication – have no use for data plane node
> implementations, and so on, and so forth.
>
> Instead, create a client library which contains ip_types_api.c and similar
> xxx_api.c files, and link the
Christan,
>>> There are some error counters that aren't errors, then there are statistic
>>> counters.
>>>
>>> I'm curious did one come before the other? I ask b/c some nodes count
>>> non-error statistics using errors (e.g., arp, ipsec, ...) and I'm wondering
>>> why.
>>
>> The node errors a
Anyone else come across this weirdness in the FD.io VPP Clang Debug Build
: && ccache /usr/lib64/ccache/clang --target=x86_64-linux-gnu
-Wno-address-of-packed-member -march=corei7 -mtune=corei7-avx -g -O0
-DCLIB_DEBUG -DFORTIFY_SOURCE=2 -fstack-protector-all -fPIC -Werror
-flax-vector-conversio
Hi Ray,
> Anyone else come across this weirdness in the FD.io VPP Clang Debug Build
Yes, it is fixed in master and 19.08 with https://gerrit.fd.io/r/c/vpp/+/22649
Best
ben
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15060): https://lists.fd.io
Hi,
By Refering : https://wiki.fd.io/view/VPP/Software_Architecture#Format , In
production images, clib_warnings result in syslog entries.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15061): https://lists.fd.io/g/vpp-dev/message/15061
Mute This
Coverity run failed today.
Current number of outstanding issues are 2
Newly detected: 0
Eliminated: 0
More details can be found at
https://scan.coverity.com/projects/fd-io-vpp/view_defects
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15062): ht
Interesting - Clang interprets the forward declaration as almost a statement of
intent,
that the implementation is coming ...
Ray K
> -Original Message-
> From: vpp-dev@lists.fd.io On Behalf Of Benoit
> Ganne (bganne) via Lists.Fd.Io
> Sent: Monday 6 January 2020 12:49
> To: Kinsella,
Hi Satya,
VCL is a library applications can link against to interact with vpp’s host
stack in a way similar to but not quite POSIX compliant. That is, it can be
used to open sessions with various transports (e.g., tcp, quic, tls) to
send/receive data in a synchronous and asynchronous manner. T
Our OpenStack cloud provider is having issues with network controller
and that affects our CI OpenStack infrastructure accross all projects.
We're working with the provider to fix the issue as quickly as possible.
Please feel free to check the status page for additional updates.
https://status.li
A fix has been implemented. Services have been restored. If you
experience any further issues, please open a ticket at
support.linuxfoundation.org.
Thank you,
Vanessa
On 1/6/20 1:03 PM, Vanessa Valderrama wrote:
> Our OpenStack cloud provider is having issues with network controller
> and that a
From: Terry
Date: Monday 6 January 2020 at 23:51
To: "Neale Ranns (nranns)"
Cc: "vpp-dev@lists.fd.io"
Subject: Re:Re:Re: [vpp-dev] vpp19.08 ipsec issue
[trim]
And when I ping 192.168.1.2 from 100.0.0.3(user1), the TRACE packet information
is as follows:
Packet 1
00:38:45:983763: handoff_tr
From: Terry
Date: Tuesday 7 January 2020 at 13:12
To: "Neale Ranns (nranns)"
Cc: "vpp-dev@lists.fd.io"
Subject: Re:Re: [vpp-dev] vpp19.08 ipsec issue
Hi Neale,
My understanding is that the interface GigabitEthernet2/1/0 should only protect
traffic from 100.0.0.0/24 and 172.168.1.0/24 and le
Hi Ezpeer :
Thank you for you advice.
I did a test to update X710's driver(i40e) and X710's Firmware:
i40e's new version : 2.10.19.30
Firmware's new version : 6.80 (inter delete NVM's 7.0 and 7.1 verison files
because they introduced some serious errors).
(I will try again when inter republish NV
hello
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15070): https://lists.fd.io/g/vpp-dev/message/15070
Mute This Topic: https://lists.fd.io/mt/69496209/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
It is likely a resource problem – when VPP requests more descriptors and/or
TX/RX queues for the NIC than the firmware has, DPDK fails to initialize the
interface. There are few ways to figure out what the problem is.
1. Bypass VPP and run testpmd with debug options turned on, something like
VPP crash when start nginx start with ldp. vpp code is master
78565f38e8436dae9cd3a891b5e5d929209c87f9,
The crash stack is below: Anyone has any solution?
>
> DBGvpp# 0: vl_api_memclnt_delete_t_handler:277: Stale clnt delete index
> 16777215 old epoch 255 cur epoch 0 0:
> /home/dev/code/net-base/
Hi Florin,
Thank you very much for quick inputs. I have gone through your youtube video
from kubecon and it cleared lot of my doubts.
You presented it in a very clear manner.
As you rightly pointed out, VppCom will be a overhead for our use case.
All we need is just a shared memory communicatio
If you want to use vfio-pci, you might want to check:
# dmesg | grep Virtualization
[5.208330] DMAR: Intel(R) Virtualization Technology for Directed I/O
If you don’t see above, vfio-pci will not work and the fix is to enable Intel
VT-d in BIOS.
Also, uio_pci_generic won’t work with i40e, and
19 matches
Mail list logo
