Hi,
We are plan to implement application based on VPP with following architecture.
The application is running on container. All traffic will be received by
physical NIC take over by VPP via DPDK. Data plane traffic will be handled by
nodes developed by ourselves, and control plane traffic
Lollita,
> We are plan to implement application based on VPP with following
> architecture. The application is running on container. All traffic will be
> received by physical NIC take over by VPP via DPDK. Data plane traffic will
> be handled by nodes developed by ourselves, and control plane
Hello,
Currently sampling rate is fixed and can not be changed. However there is a
patch https://gerrit.fd.io/r/#/c/9671/3 which is in review process to set the
poller frequency.
You can have a look at it.?
Cheers,
Mohsin
From: vpp-dev@lists.fd.io
Guys,
I'd like to clean up these warnings.
If anyone feels responsible for these please go ahead and do the magic!
WARNING:vppapigen:/vpp/papi-fixes/build-data/../src/vlibmemory/memclnt.api:0:1:
Old Style VLA: u8 data[0];
In case of memclnt that’s actually a void pointer to be passed to the rpc
handler. Unless it complicates life for the API generator, not sure if it’s
worth adding the size to the struct.
Florin
> On Mar 1, 2018, at 9:26 AM, Ole Troan wrote:
>
> Guys,
>
> I'd like to
Hi all,
I am facing an issue with building VPP with DPDK (Mellanox Drivers
enabled) on aarch64.
The OFED version installed:
$ ofed_info -s
MLNX_OFED_LINUX-4.2-1.2.0.0:
Kernel Version:
$ uname -r
4.10.0-28-generic
Operating System Version:
Ubuntu 16.04.4 LTS (GNU/Linux 4.10.0-28-generic
Hi, Ole.
Thank you for update. I have do quick browse on the source code of
"punt socket", but what is your consider about supporting VRF?
BR/Lollita Liu
-Original Message-
From: Ole Troan [mailto:otr...@employees.org]
Sent: Thursday, March 01, 2018 6:35 PM
To: Lollita Liu
Hi folks,
So the LFN TAC is looking to close on the “Community goals and priorities”
rollup by 9th March.
This exercise is part of the process of obtaining a fair share of resources for
FD.io in 2018.
So if you haven’t already, please canvass your committers and contributors for
their 2018