For MPLS-over-UDP, the NIC does RSS. For MPLS-over-GRE, vrouter-dpdk hashes and distributes the packets across CPU cores in software. It doesn’t need a separate interface (such as pkt3) with DPDK. The kernel module needs it as it uses the Linux RPS functionality, which requires an interface.
Raja From: kevin parrikar <kevin.parker...@gmail.com> Date: Thursday, November 24, 2016 at 9:08 AM To: Raja Sivaramakrishnan <r...@juniper.net> Cc: dev <dev@lists.opencontrail.org>, "<us...@lists.opencontrail.org>" <us...@lists.opencontrail.org> Subject: Re: [Users] taskset cpu affinity not considered when starting vrouter-dpdk eventhough its set in contrail-vrouter-dpdk.ini Wow!! thanks Raja, Never thought about that after checking the logs its clear now, 5 threads are not assigned to any CPU and rest are all pinned 1:1 :) Regarding distribution of packets to to those cores,in kernel mode vrouter there is pkt3 interface to do packet distribution,in DPDK-vrouter i dont see that interface in vif --list,how is it achieved in DPDK-Vrouter with out this interface . Thanks again On Thu, Nov 24, 2016 at 12:27 AM, Rajagopalan Sivaramakrishnan <r...@juniper.net<mailto:r...@juniper.net>> wrote: Hi Kevin, The forwarding threads with vrouter-dpdk use the cores specified in the testbed file. Other threads in vrouter-dpdk (which don’t consume as much CPU) can run on any core. Please see “—lcores” argument in /var/log/contrail/contrail-vrouter-dpdk-stdout.log. Raja From: Users <users-boun...@lists.opencontrail.org<mailto:users-boun...@lists.opencontrail.org>> on behalf of kevin parrikar <kevin.parker...@gmail.com<mailto:kevin.parker...@gmail.com>> Date: Tuesday, November 22, 2016 at 11:28 AM To: dev <dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>>, "<us...@lists.opencontrail.org<mailto:us...@lists.opencontrail.org>>" <us...@lists.opencontrail.org<mailto:us...@lists.opencontrail.org>> Subject: [Users] taskset cpu affinity not considered when starting vrouter-dpdk eventhough its set in contrail-vrouter-dpdk.ini Hello All, I have contrail with DPDK up and running but i think taskset set in "contrail-vrouter-dpdk.ini" is not considered and its using default cpu affinity of "fff...." on compute nodes taskset -c -p `pidof contrail-vrouter-dpdk` pid 46767's current affinity list: 0-47 Version: 3.0.2.0-51 configuration: cat /etc/contrail/supervisord_vrouter_files/contrail-vrouter-dpdk.ini [program:contrail-vrouter-dpdk] command=taskset 1,5,6,7 /usr/bin/contrail-vrouter-dpdk --no-daemon --vr_mpls_labels 5000 --vr_flow_entries=2097152 --vdev "eth_bond_bond1,mode=0,xmit_policy=l34,socket_id=0,mac=00:11:0a:6d:06:94,slave=0000:08:00.0,slave=0000:81:00.1" --vlan_tci "14" --vlan_fwd_intf_name "bond1" --socket-mem 1024,1024 priority=410 autostart=True killasgroup=True stdout_capture_maxbytes=1MB redirect_stderr=True stdout_logfile=/var/log/contrail/contrail-vrouter-dpdk-stdout.log stderr_logfile=/var/log/contrail/contrail-vrouter-dpdk-stderr.log exitcodes=0 loglevel=debug on Contrail.log i dont see taskset being used to start dpdk-vrouter and hence i suppose the issue is in "vrouter-pre-start.sh" .Could this be a bug. if i manually execute above command then taskset gives proper result. Thanks for any help Regards, Kevin
_______________________________________________ Dev mailing list Dev@lists.opencontrail.org http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
