All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karsten Desler <kdesler@soohrt.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: _High_ CPU usage while routing (mostly) small UDP packets
Date: Mon, 6 Dec 2004 23:41:07 +0100	[thread overview]
Message-ID: <20041206224107.GA8529@soohrt.org> (raw)
In-Reply-To: <20041206134849.498bfc93.davem@davemloft.net>

* David S. Miller wrote:
> It's spending nearly half of it's time in iptables.
> Try to consolidate your rules if possible.  This is the
> part of netfilter that really doesn't scale well at all.
> 

Removing the iptables rules helps reducing the load a little, but the
majority of time is still spent somewhere else.

50kpps rx and 43kpps tx.
procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 0  0      0 1802956 101032 104464    0    0     0    18   74    26  0 21 79  0
 0  0      0 1802956 101032 104464    0    0     0    61 8810    28  0 25 75  0
 0  0      0 1802956 101032 104464    0    0     0   233 8867    17  0 24 76  0
 0  0      0 1802892 101032 104464    0    0     0     0 8865    16  0 21 79  0
 0  0      0 1802892 101032 104464    0    0     0     0 8772     8  0 18 82  0 <- iptables -F
 0  0      0 1802892 101032 104464    0    0     0    36 8863    18  0 19 81  0
 0  0      0 1802892 101032 104464    0    0     0    80 8700    18  0 18 82  0
 0  0      0 1802956 101032 104464    0    0     0     0 8779     7  0 17 83  0
 0  0      0 1802948 101032 104464    0    0     0   223 8716   278  4 19 76  0

- Karsten

  reply	other threads:[~2004-12-06 22:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 20:53 _High_ CPU usage while routing (mostly) small UDP packets Karsten Desler
2004-12-06 21:48 ` David S. Miller
2004-12-06 22:41   ` Karsten Desler [this message]
2004-12-06 23:53     ` Bernd Eckenfels
2004-12-07  0:20       ` Karsten Desler
2004-12-07  2:46         ` jamal
2004-12-07  2:54           ` Karsten Desler
2004-12-07  3:18             ` jamal
2004-12-07  3:24               ` Karsten Desler
2004-12-07  3:30                 ` jamal
2004-12-07  4:02                   ` Karsten Desler
2004-12-07 10:21                     ` Karsten Desler
2004-12-07 12:34                       ` jamal
2004-12-07 13:14                         ` Karsten Desler
2004-12-06 23:56     ` Con Kolivas
2004-12-07  0:18       ` Karsten Desler
2004-12-07 10:47     ` P
2004-12-07 11:21       ` Karsten Desler
2004-12-07 12:38         ` Robert Olsson
2004-12-07 12:50           ` Karsten Desler
2004-12-07 13:04             ` jamal
2004-12-07 13:11               ` Karsten Desler
2004-12-07 13:39               ` P
2004-12-07 18:38         ` Karsten Desler
2004-12-08  5:39         ` Willy Tarreau
2004-12-08 13:08           ` Karsten Desler
2004-12-08 13:27             ` jamal
2004-12-07 21:10 ` Karsten Desler
2004-12-07 22:40   ` Robert Olsson
2004-12-08 22:06     ` Karsten Desler
2004-12-08  4:31   ` jamal
2004-12-08 13:26     ` Karsten Desler

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=20041206224107.GA8529@soohrt.org \
    --to=kdesler@soohrt.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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.