ksoftirq consumes >80% CPU on embedded platform

Do you have a question? Post it now! No Registration Necessary

Translate This Thread From English to

Threaded View
Mark Contact options for registered users 's Avatar (by Gravatar) posted on
July 28, 2010, 2:29 am
rate this thread
Reply to this post Reply Tag this thread to save it in your account Save Printer-friendly version of this post Print
Hello,

we're designing SOHO router based on MIPS processor, wired up with 24-ports
switch. The CPU runs NAT (configured with iptables), iptables rules, dhcp
etc. it doesn't have any H/W acceleration for these functions. When testing
NAT in full-mesh mode (i.e. one WAN port and others are LAN port), we
observe the significant system's slowdown, especially console responds very
slowly, and there is also packets loss.
The 'top' shows that ksoftirqd consumes over 80% of CPU.

What can be the reason of such behaviour? As I know Linux NAT runs in kernel
space, so it should not be a problem of context switching?

--
Mark


Other Related Threads
David Schwartz Contact options for registered users 's Avatar (by Gravatar) posted on
July 28, 2010, 11:04 pm
Permalink
Reply to this post Reply Tag this thread to save it in your account Save Printer-friendly version of this post Print
Re: ksoftirq consumes >80% CPU on embedded platform

Quoted text here. Click to load it

It sounds like the CPU just doesn't have the horsepower to do all the
tasks it is doing. How many packets per second, and how many
connections, are you NATing? What MIPS processor is this?

DS

Other Related Threads
Jorgen Grahn Contact options for registered users 's Avatar (by Gravatar) posted on
August 9, 2010, 7:34 pm
Permalink
Reply to this post Reply Tag this thread to save it in your account Save Printer-friendly version of this post Print
Re: ksoftirq consumes >80% CPU on embedded platform
["Followup-To:" header set to comp.os.linux.networking.]
Quoted text here. Click to load it

Get the mpstat(1) command and check the output from mpstat -P ALL <n>
to get a different view of it (or check the files in /proc which give
you the same info, except in raw form).

mpstat(1) is part of the sar package, I think.

Quoted text here. Click to load it

/Jorgen

--
  // Jorgen Grahn <grahn@  Oo  o.   .  .
\X/     snipabacken.se>   O  o   .

Site Timeline