Paul Emmerich
Paul Emmerich
That should work, not sure what is going on here, I'll need to test this on real hardware; I'll get back to this
libmoon expects `CONFIG_RTE_MAX_LCORE=128` (and tries to use the last cores for our shared tasks), however, you should be able to change that to 256 here: https://github.com/libmoon/libmoon/blob/master/lua/dpdk.lua#L160
Virtual devices aren't the best match because we heavily rely on hardware features and multiple queues. You can increase the number of queues on virtio, but you'll get a much...
the virtual NIC doesn't support hardware filters which the moongen-simple ARP relies on. there's a way to put arp packets manually into the ARP task, example: https://github.com/libmoon/libmoon/blob/master/examples/dump-pkts.lua#L97 maybe it's easier...
can you try with l2-load-latency instead? Or try to use multiple threads. The bottleneck are UDP checksums on some systems (despite offloading)
Jumbo frame support is still somewhat poor in MoonGen, sorry. The main reason for this is that we are aiming at high packet rates (the thing that software packet generators...
Which firmware version are you using? It should be printed on startup during DPDK initialization. > Am 07.03.2018 um 02:11 schrieb sekhonramneek : > > Hi > I am trying...
We are currently also tracking down problems with firmware 6.01. These problems don't appear on firmware 5.04. 5.05 is also unfortunately broken in different ways (no timestamping, see errata sheet).
Please post the full output.
thanks! I'll add something in the port configuration to enable jumbo frames manually.