On 31.10.2019 17:27, David Marchand wrote:
On Thu, Oct 31, 2019 at 4:35 PM David Marchand
<[email protected]> wrote:
# sudo -u openvswitch XDG_RUNTIME_DIR=/var/run/openvswitch
./dpdk/v18.11.2/app/dpdk-pdump -- --pdump
18.11.2 ? Looks suspicious.
'port=0,queue=*,rx-dev=/tmp/pkts.pcap,tx-dev=/tmp/pkts.pcap'
EAL: Detected 28 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket
/var/run/openvswitch/dpdk/rte/mp_socket_85457_497b63ab1c2d10
EAL: Probing VFIO support...
EAL: VFIO support initialized
Hum, looks like something is broken in master, when capturing packets:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f03c6d31700 (LWP 98102)]
bucket_dequeue_orphans (n_orphans=251, obj_table=0x14fe83a10,
bd=0x14fe006c0) at
/root/dpdk/drivers/mempool/bucket/rte_mempool_bucket.c:194
194 rc = rte_ring_dequeue(bd->shared_bucket_ring,
I will have to start with a clean environment, just in case I broke
something when switching ovs / dpdk build dirs.
But I don't have the time now, maybe next week.
You also need to re-check that your threads are not running on the
same cores which is hard, because OVS uses non-eal threads and
non-pmd threads could float over the free system cores.
All this multiprocessing in DPDK is too dangerous to use IHMO.
From my experience, if you trying to run 2 DPDK applications
on the same memory, one of them will definitely crash. At least
on a first few attempts.
'--in-memory' is the best option. It'll be probably cool to enable
it by default. :)
Best regards, Ilya Maximets.
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
