netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karsten Desler <kdesler@soohrt.org>
To: netdev@oss.sgi.com
Cc: linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>, jamal <hadi@cyberus.ca>,
	Robert Olsson <Robert.Olsson@data.slu.se>,
	P@draigBrady.com
Subject: Re: _High_ CPU usage while routing (mostly) small UDP packets
Date: Tue, 7 Dec 2004 22:10:35 +0100	[thread overview]
Message-ID: <20041207211035.GA20286@quickstop.soohrt.org> (raw)
In-Reply-To: <20041206205305.GA11970@soohrt.org>

[-- Attachment #1: Type: text/plain, Size: 400 bytes --]

Karsten Desler <kdesler@soohrt.org> wrote:
> Current packetload on eth0 (and reversed on eth1):
>   115kpps tx
>   135kpps rx

I totally forgot to mention: There are approximately 100k concurrent
flows.

>From dmesg:
IP: routing cache hash table of 16384 buckets, 128Kbytes

Maybe there is some contention on the rt_hash_table spinlocks?
Is the attached patch enough to increase the size?

- Karsten

[-- Attachment #2: rtcachesize.patch --]
[-- Type: text/plain, Size: 472 bytes --]

--- linux/net/ipv4/route.c~old	2004-12-07 21:55:22.000000000 +0100
+++ linux/net/ipv4/route.c	2004-12-07 21:55:32.000000000 +0100
@@ -2728,7 +2728,7 @@
 	if (!ipv4_dst_ops.kmem_cachep)
 		panic("IP: failed to allocate ip_dst_cache\n");
 
-	goal = num_physpages >> (26 - PAGE_SHIFT);
+	goal = num_physpages >> (23 - PAGE_SHIFT);
 	if (rhash_entries)
 		goal = (rhash_entries * sizeof(struct rt_hash_bucket)) >> PAGE_SHIFT;
 	for (order = 0; (1UL << order) < goal; order++)

  parent reply	other threads:[~2004-12-07 21:10 UTC|newest]

Thread overview: 31+ 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
2004-12-06 23:56     ` Con Kolivas
2004-12-07  0:18       ` Karsten Desler
     [not found]     ` <E1CbSf8-00047p-00@calista.eckenfels.6bone.ka-ip.net>
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-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 [this message]
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=20041207211035.GA20286@quickstop.soohrt.org \
    --to=kdesler@soohrt.org \
    --cc=P@draigBrady.com \
    --cc=Robert.Olsson@data.slu.se \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).