Hi all,
we've been experiencing with OVS and its patch ports, and we set up a
the following case:
One OVS bridge instance (created via add-br) is connected to two
physical interfaces (our two-port Intel X710 NIC), and with an arbitrary
number of patch ports (we used 12,24,36,48, etc.) this OVS bri
Hi!
You may can use *perf* as well. However, it only works well with kernel
space drivers.
For DPDK drivers, *valgrind* and *callgrind* could be a better solution.
On 07/20/2016 09:58 PM, Christopher Mansour wrote:
> Thanks Ben for your feedback. I already tried that, I was wondering whether I
Thanks!
I will definitely try this.
On 07/06/2016 01:59 AM, Justin Pettit wrote:
On Jul 4, 2016, at 4:50 AM, Levente Csikor wrote:
Hi,
I did not find any documented limit about the number of patchports, so I wrote
a simple script, which adds a predefined number of patchports and some dummy
Hi,
That manual is only for installing OVS and linking it to DPDK.
However, you need to install DPDK on your own before installing OVS with
DPDK.
download DPDK from here: http://dpdk.org/download
follow instructions for the installation procedure (not that difficult -
less commands needed tha
Yepp, Ben has right.
There are a bunch of performance analyses on the Internet that presents
the throughput of software based switches, like OVS, using multiple cores.
If your traffic is really simple (like a packet generator's simple
pattern, i.e., when all header information are the same for
Hi,
I did not find any documented limit about the number of patchports, so I
wrote a simple script, which adds a predefined number of patchports and
some dummy rules into the flow tables to actually have some reason for
the whole stuff.
First, I tried to add 100 and 1000 patchports between t
