+1, thanks Ray...
-----Original Message-----
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Kinsella, Ray
Sent: Tuesday, October 18, 2016 10:17 AM
To: Miguel Angel Muñoz Gonzalez <miguel.angel.munoz.gonza...@ericsson.com>;
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Vpp_main running at 100% CPU
Hi Miguel,
Most your time is being spent in dpdk_input and vhost_user_input.
Are you running VPP in a VM or on the host?
I ask because vhost_user_input suggests you are running on the host?
If you are running in a VM and you are using software interfaces (no PCI
passhrough) you might try using vpp-lite with the af_packet interface
instead of dpdk_input as you will likely get similar performance without
DPDK polling.
Ray K
On 18/10/2016 14:53, Miguel Angel Muñoz Gonzalez wrote:
> Thanks Ray. Yes, in startup.conf I set:
>
> dpdk {
> dev 0000:00:08.0
> uio-driver uio_pci_generic
> }
>
> And this is the output of 'show run' though to be honest I'm not very
> familiar with it yet:
>
> Time 228.9, average vectors/node 1.19, last 128 main loops 0.00 per node 0.00
> vector rates in 4.4491e1, out 3.9918e0, drop 4.3451e1, punt 1.0394e0
> Name State Calls Vectors
> Suspends Clocks Vectors/Call
> GigabitEthernet0/8/0-output active 914 914
> 0 1.70e3 1.00
> GigabitEthernet0/8/0-tx active 914 914
> 0 6.58e4 1.00
> admin-up-down-process event wait 0 0
> 1 1.32e4 0.00
> api-rx-from-ring active 0 0
> 1445 1.59e5 0.00
> arp-input active 1147 1224
> 0 2.03e4 1.07
> cdp-process any wait 0 0
> 134 2.37e3 0.00
> dhcp-client-process any wait 0 0
> 3 6.04e3 0.00
> dpdk-input polling 524816917 10187
> 0 8.11e6 0.00
> dpdk-process any wait 0 0
> 76 1.53e6 0.00
> error-drop active 8138 9949
> 0 2.42e3 1.22
> error-punt active 238 238
> 0 8.85e3 1.00
> ethernet-input active 8289 10187
> 0 5.47e3 1.23
> flow-report-process any wait 0 0
> 1 6.45e3 0.00
> gmon-process time wait 0 0
> 46 1.43e7 0.00
> icmp6-neighbor-solicitation active 107 123
> 0 4.26e3 1.15
> ip4-arp active 946 971
> 0 1.03e4 1.03
> ip4-input active 5818 7181
> 0 3.24e3 1.23
> ip4-lookup active 1229 1401
> 0 4.53e3 1.14
> ip4-lookup-multicast active 4601 5760
> 0 5.57e3 1.25
> ip4-miss active 4948 6190
> 0 2.11e3 1.25
> ip6-hop-by-hop active 137 147
> 0 2.26e3 1.07
> ip6-icmp-input active 107 123
> 0 1.45e3 1.15
> ip6-icmp-neighbor-discovery-ev any wait 0 0
> 226 8.55e3 0.00
> ip6-input active 1437 1544
> 0 3.88e3 1.07
> ip6-local active 244 270
> 0 2.81e3 1.11
> ip6-lookup active 1437 1544
> 0 4.71e3 1.07
> ip6-miss active 1202 1274
> 0 4.16e3 1.06
> lisp-retry-service any wait 0 0
> 113 9.63e3 0.00
> startup-config-process done 1 0
> 1 1.56e4 0.00
> unix-epoll-input polling 524526101 0
> 0 8.25e2 0.00
> vhost-user-input polling 500057376 0
> 0 1.43e2 0.00
> vhost-user-process any wait 0 0
> 69 1.31e4 0.00
> vpe-link-state-process event wait 0 0
> 3 1.14e4 0.00
> vpe-oam-process any wait 0 0
> 111 1.09e4 0.00
> vpe-route-resolver-process any wait 0 0
> 3 1.19e4 0.00
>
> Thank you very much!!
> Best Regards,
> Miguel Ángel.
>
> -----Original Message-----
> From: Kinsella, Ray [mailto:ray.kinse...@intel.com]
> Sent: martes, 18 de octubre de 2016 15:29
> To: Miguel Angel Muñoz Gonzalez <miguel.angel.munoz.gonza...@ericsson.com>;
> vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Vpp_main running at 100% CPU
>
> Hi Miguel,
>
> If you are using DPDK - it would be my expectation yes.
> Can you do a 'show run' in vppctl to see where time is being spent.
>
> Ray K
>
> On 18/10/2016 09:02, Miguel Angel Muñoz Gonzalez wrote:
>> Hi,
>>
>> In SFC project from ODL we are trying to use VPP to run a simple
>> scenario with basic service chain setup. At the moment I'm running
>> vpp
>> 1609 with honeycomb in Centos7, as a VirtualBox VM.
>>
>> Once VPP is started, 'top' command shows vpp_main process taking 100%
>> CPU in one of the cores and never goes down. Is this normal?
>>
>> I have VT-x/AMD-V/PAE/NX extensions activated.
>>
>>
>>
>> Thank you,
>>
>> Best Regards,
>>
>> Miguel Ángel.
>>
>>
>>
>>
>>
>> [root@localhost vagrant]# top -b -n1
>>
>> top - 07:52:02 up 2:16, 4 users, load average: 1.16, 1.25, 1.31
>>
>> Tasks: 197 total, 3 running, 194 sleeping, 0 stopped, 0 zombie
>>
>> %Cpu(s): 21.7 us, 17.5 sy, 0.0 ni, 60.6 id, 0.1 wa, 0.0 hi, 0.1
>> si,
>> 0.0 st
>>
>> KiB Mem : 10163584 total, 2786344 free, 4864612 used, 2512628
>> buff/cache
>>
>> KiB Swap: 1572860 total, 1572860 free, 0 used. 4967176 avail Mem
>>
>>
>>
>> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>>
>> 8033 root 20 0 1933980 30820 4952 R 100.0 0.3 89:25.57 vpp_main
>>
>> 1 root 20 0 126600 7424 2628 S 0.0 0.1 0:01.75 systemd
>>
>> 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
>>
>> 3 root 20 0 0 0 0 S 0.0 0.0 0:00.18
>> ksoftirqd/0
>>
>> 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00
>> kworker/0:0H
>>
>> 6 root 20 0 0 0 0 S 0.0 0.0 0:00.68
>> kworker/u4:0
>>
>> 7 root rt 0 0 0 0 S 0.0 0.0 0:00.07
>> migration/0
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> vpp-dev mailing list
>> vpp-dev@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/vpp-dev
>>
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
