CloudEOS and vEOS-DPDK Mode Verification

To check if CloudEOS and vEOS is running in DPDK mode, verify if the “sfe” agent is running using the following command.

switch#show agent sfe ping
 
show agent sfe ping
Agent Name Last Ping Max PingMax Ping Response SeenLast Ping Response Seen
---------------------- ------------- ----------------------------------- ------------------------
Sfe1.571 ms 2209.819 ms 2019-11-15 11:14:05 2019-12-12 15:02:48

A system in DPDK mode uses 100% of CPU cycles for each datapath vCPU. This is normal and expected. To ensure that packet forwarding tasks, which are CPU intensive, do not starve control plane and management operations, EOS dedicates CPU cores for control/management functions.

Linux “top” command followed by typing “1” when “top” is running is used to get detailed CPU utilization. The below output shows “top” results for a CloudEOS and vEOS with 2 cores. Depending on the version either “Sfe” or “bessd” will show using the 100% of the datapath core.


vEOS-CLI(config)#bash top -n 1

Tasks: 236 total, 1 running, 235 sleeping, 0 stopped, 0 zombie
%Cpu0:1.6 us,0.7 sy,0.0 ni, 95.1 id,0.0 wa,2.6 hi,0.0 si,0.0 st
%Cpu1:100.0 us,0.0 sy,0.0 ni,0.0 id,0.0 wa,0.0 hi,0.0 si,0.0 st
KiB Mem: 8122156 total,4642632 used,3479524 free, 255624 buffers
KiB Swap:0 total,0 used,0 free,1857744 cached
 
PID USERPRNIVIRTRESSHR S%CPU %MEMTIME+COMMAND
 3355 root20 0 2186m 239m 201m S 100.13.039262:38 Sfe [or bessd]
 2544 root20 0375m58m38m S 0.30.7 192:36.08 ProcMgr-worker
 2705 root20 0403m 180m 142m S 0.32.3 135:53.49 Sysdb
 3102 root20 0379m 111m95m S 0.31.4 8:06.90 Ira
 3119 root20 0373m86m70m S 0.31.124:34.26 StpTxRx