From: Marek Kierdelewicz <marek@piasta.pl>
To: Steve Fink <sphink@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: CPU usage of simple DROP rule
Date: Tue, 29 Sep 2009 21:27:44 +0200 [thread overview]
Message-ID: <20090929212744.6679cfec@catlap> (raw)
In-Reply-To: <7d7f2e8c0909291131m5cd58372ta5907f1612d8fa05@mail.gmail.com>
Hello
>I have a single OUTPUT rule (drop a particular UDP host:port) that
>...
>My 8 cores are all at about 30% usage when I have no rules defined
>(and the packets are going out to the switch). When I add that rule,
>one of the cores shoots to 100%, another to 70% or so. The rest don't
>really change.
Looks like two cores are being hit by ksoftirqd. There are some paths
you can explore to achieve lower cpu usage/better core-load
distribution:
- try using smp_affinity - bind different nic irqs to different cores;
you can also use bonding to achieve better traffic distribution
among nics;
- are you using intel i/o at dma support? it should lower network
overhead for localy generated traffic;
- try adjusting nic coalesce parameters - it should lower network
cpu overhead at the cost of higher latency;
Cheers
Marek Kierdelewicz
next prev parent reply other threads:[~2009-09-29 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 18:31 CPU usage of simple DROP rule Steve Fink
2009-09-29 19:27 ` Marek Kierdelewicz [this message]
2009-09-29 19:45 ` Steve Fink
2009-09-30 8:02 ` Marek Kierdelewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090929212744.6679cfec@catlap \
--to=marek@piasta.pl \
--cc=netfilter@vger.kernel.org \
--cc=sphink@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.