CPU load of AirGrid by ksoftirqd process

Question

linux

Hello dear.
On AirGrid M5HP (v5.5.3), pings regularly increase via ethernet from 10 to 400-500 ms, and after a while it falls off completely, like everything behind it. configured as station. Once, before the dump, I managed to see such a picture - the whole process is eating the ksoftirqd process - what is it and how to deal with it?

XM.v5.5.3# uname -a
Linux SE5rx 2.6.32.54 #1 Fri Oct 12 17:17:33 EEST 2012 mips unknown

Mem: 24536K used, 4988K free, 0K shrd, 3404K buff, 9976K cached
CPU:   0% usr   0% sys   0% nice   5% idle   0% io   2% irq  90% softirq
Load average: 3.11 1.59 0.69
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
    3     2 admin    RW       0   0%  44% [ksoftirqd/0]
    4     2 admin    SW       0   0%  27% [events/0]
 1376  1309 admin    S     1996   7%   8% /bin/dropbear -F -d /etc/persistent/d
 1411  1408 admin    R     1972   7%   4% top
 1308     1 admin    R     4216  14%   4% /bin/lighttpd -D -f /etc/lighttpd.con
   52     2 admin    SW       0   0%   4% [bdi-default]
 1159     1 admin    S <   1964   7%   3% /bin/watchdog -t 1 /dev/watchdog
 1304     1 admin    S     6272  21%   0% /bin/infctld -m -c -d
 1309     1 admin    S     1940   7%   0% /bin/dropbear -F -d /etc/persistent/d
 1305     1 admin    S     1968   7%   0% /bin/syslogd -n -S
    1     0 admin    S     1976   7%   0% init
 1408  1376 admin    S     1976   7%   0% -sh
  944     1 admin    S     1976   7%   0% init
 1306     1 admin    S     1500   5%   0% /usr/bin/iwevent -s
 1307     1 admin    S     1392   5%   0% /sbin/ntpclient -n -s -c 0 -l -h 192.
  492     1 admin    S     1140   4%   0% /sbin/hotplug2 --persistent --set-rul
  165     2 admin    SW       0   0%   0% [mtdblockd]
   50     2 admin    SW       0   0%   0% [sync_supers]
    5     2 admin    SW       0   0%   0% [khelper]
    2     0 admin    SW       0   0%   0% [kthreadd]

Thanks in advance for the tips.

Answer 1

In general, apparently, the reason was a large number of pps with WDS turned off. The inclusion of WDS, apparently, significantly offloaded the processor.
Basically, it's logical.

Answer 2

Thank you. There was a similar problem. Enabling WDS on one of the sides (there was such) reduced the CPU load