search

smadaminov / ovs-dpdk-meson-issues

VMware Summer 2021
BSD 3-Clause "New" or "Revised" License
1 stars 1 forks source link

No non-isolated pmd #75

Open williamtu opened 2 years ago

williamtu commented 2 years ago 
2021-10-02T02:48:10Z|00053|dpif_netdev|INFO|Performing pmd to rx queue assignment using cycles algorithm.
2021-10-02T02:48:10Z|00054|dpif_netdev|WARN|No non-isolated pmd on any numa available for port 'p0' rx queue 0 (measured processing cycles 0). This rx queue will not be polled.
williamtu commented 2 years ago

OVS discover 0 NUMA node and 0 CPU cores.

EAL: lib.rcu log level changed from disabled to error
2021-10-02T03:05:22Z|00001|vlog|INFO|opened log file c:/openvswitch/var/log//ovs-vswitchd.log
2021-10-02T03:05:22Z|00002|ovs_numa|INFO|Discovered 0 NUMA nodes and 0 CPU cores
2021-10-02T03:05:22Z|00003|reconnect|INFO|unix:c:/openvswitch/var/run//db.sock: connecting...
2021-10-02T03:05:22Z|00004|reconnect|INFO|unix:c:/openvswitch/var/run//db.sock: connected
williamtu commented 2 years ago

in OVS, the lib\ovs-numa.c is linux specific. no Windows support. For Windows, see eal_create_cpu_map(void) in DPDK GetLogicalProcessorInformationEx

OVS, instead, can do a dummy config

/* Has the same effect as discover_numa_and_core(), but instead of
 * reading sysfs entries, extracts the info from the global variable
 * 'dummy_config', which is set with ovs_numa_set_dummy().
 *
 * 'dummy_config' lists the numa_ids of each CPU separated by a comma, e.g.
 * - "0,0,0,0": four cores on numa socket 0.
 * - "0,1,0,1,0,1,0,1,0,1,0,1,0,1,0,1": 16 cores on two numa sockets.
 * - "0,0,0,0,1,1,1,1": 8 cores on two numa sockets.
 * - "0,0,0,0,8,8,8,8": 8 cores on two numa sockets, non-contiguous.

use ovs-vswitchd.exe --pidfile -vfile:info --log-file --disable-system --dummy-numa=”0,0,0,0,0,0”


2021-10-02T03:27:00Z|00040|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports ct_orig_tuple6
2021-10-02T03:27:00Z|00041|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath supports IPv6 ND Extensions
2021-10-02T03:27:00Z|00042|ofproto_dpif_upcall|INFO|Setting n-handler-threads to 8, setting n-revalidator-threads to 4
2021-10-02T03:27:00Z|00043|ofproto_dpif_upcall|INFO|Starting 12 threads
2021-10-02T03:27:00Z|00044|dpif_netdev|INFO|pmd-rxq-affinity isolates PMD core
2021-10-02T03:27:00Z|00045|dpif_netdev|INFO|PMD auto load balance interval set to 1 mins
2021-10-02T03:27:00Z|00046|dpif_netdev|INFO|PMD auto load balance improvement threshold set to 25%
2021-10-02T03:27:00Z|00047|dpif_netdev|INFO|PMD auto load balance load threshold set to 95%
2021-10-02T03:27:00Z|00048|dpif_netdev|INFO|PMD auto load balance is disabled
2021-10-02T03:27:00Z|00049|netlink_socket|ERR|fcntl: The system cannot find the file specified.
2021-10-02T03:27:00Z|00050|bridge|INFO|bridge br0: added interface br0 on port 65534
2021-10-02T03:27:00Z|00051|dpif_netdev|INFO|PMD thread on numa_id: 0, core id:  3 created.
2021-10-02T03:27:00Z|00052|dpif_netdev|INFO|PMD thread on numa_id: 0, core id:  0 created.
2021-10-02T03:27:00Z|00053|dpif_netdev|INFO|PMD thread on numa_id: 0, core id:  1 created.
2021-10-02T03:27:00Z|00054|dpif_netdev|INFO|PMD thread on numa_id: 0, core id:  2 created.
2021-10-02T03:27:00Z|00055|dpif_netdev|INFO|There are 4 pmd threads on numa node 0
2021-10-02T03:27:00Z|00056|netdev_dpdk|WARN|Interface p0 does not support MTU configuration, max packet size supported is 1500.