Hi, Daniele.
I like the main idea of this patch-set. I really thought to implement
something like this. Thanks for it.
I've done just a very quick look at patches. One comment posted to 11/11.
Main issue:
Patch set doesn't work for me.
I have a preconfigured database with n_rxq set for vhost-user ports.
But, after starting of vswitchd there is only one rx queue configured
per vhost-user port. And nothing changes after starting of VM.
So, VM started, ports configured, all vhost queues enabled, but only
1 queue really used by OVS.
Best regards, Ilya Maximets.
P.S. Some additional info:
<--------------------------------------------->
# ./bin/ovs-vsctl show
b9394127-803f-4952-95ce-5877b2926adc
Bridge "ovsdpdk_br0"
Port "vhost:15"
Interface "vhost:13"
type: dpdkvhostuser
options: {n_rxq="8"}
<--------------------------------------------->
# ./bin/ovs-appctl dpctl/show
netdev@ovs-netdev:
lookups: hit:0 missed:0 lost:0
flows: 0
port 0: ovs-netdev (internal)
port 1: vhost:13 (dpdkvhostuser: configured_rx_queues=8,
configured_tx_queues=8, requested_rx_queues=8, requested_tx_queues=25)
<--------------------------------------------->
# ./bin/ovs-appctl dpif-netdev/pmd-rxq-show
pmd thread numa_id 0 core_id 5:
port: vhost:13 queue-id: 0
pmd thread numa_id 0 core_id 6:
pmd thread numa_id 0 core_id 7:
pmd thread numa_id 0 core_id 8:
<--------------------------------------------->
|00136|dpdk(vhost_thread2)|DBG|TX queue mapping for
/var/run/openvswitch/vhost:13
|00137|dpdk(vhost_thread2)|DBG| 0 --> 0
|00138|dpdk(vhost_thread2)|DBG| 1 --> 1
|00139|dpdk(vhost_thread2)|DBG| 2 --> 2
|00140|dpdk(vhost_thread2)|DBG| 3 --> 3
|00141|dpdk(vhost_thread2)|DBG| 4 --> 4
|00142|dpdk(vhost_thread2)|DBG| 5 --> 5
|00143|dpdk(vhost_thread2)|DBG| 6 --> 6
|00144|dpdk(vhost_thread2)|DBG| 7 --> 7
<--------------------------------------------->
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev
