From: Robert Olsson <Robert.Olsson@data.slu.se>
To: davem@redhat.com
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com, Robert.Olsson@data.slu.se
Subject: [PATCH] option for large routing hash
Date: Tue, 9 Dec 2003 16:09:07 +0100 [thread overview]
Message-ID: <16341.58771.558850.163216@robur.slu.se> (raw)
Hello!
I think patch should be useful as it helps performance a lot during high
flow load. I have some numbers if you are interested.
Cheers.
--ro
--- net/ipv4/Kconfig.orig 2003-12-09 14:00:14.000000000 +0100
+++ net/ipv4/Kconfig 2003-12-09 14:51:27.000000000 +0100
@@ -75,6 +75,19 @@
If unsure, say N.
+config IP_ROUTE_LARGE_HASH
+ bool "IP: large routing hash"
+ ---help---
+ Say yes to increase the number of dst hash buckets. Most likely you
+ are running a server or router with lots of flows. Saying yes
+ will increase used dst hash 8 times typically from 16Kbytes to 128
+ Kbytes on a 256Mbytes system.
+
+ dst hash is otherwise tunable via /proc/sys/net/ipv4/route/
+ Monitoring can be done with rtstat utility this comes with iproute2.
+
+ If unsure, say N.
+
config IP_ROUTE_FWMARK
bool "IP: use netfilter MARK value as routing key"
depends on IP_MULTIPLE_TABLES && NETFILTER
--- net/ipv4/route.c.orig 2003-12-09 13:59:57.000000000 +0100
+++ net/ipv4/route.c 2003-12-09 14:49:48.000000000 +0100
@@ -2747,6 +2747,9 @@
goal = num_physpages >> (26 - PAGE_SHIFT);
+#ifdef CONFIG_IP_ROUTE_LARGE_HASH
+ goal <<= 3;
+#endif
for (order = 0; (1UL << order) < goal; order++)
/* NOTHING */;
next reply other threads:[~2003-12-09 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 15:09 Robert Olsson [this message]
2003-12-09 20:20 ` [PATCH] option for large routing hash David S. Miller
2003-12-09 22:28 ` Robert Olsson
2003-12-10 8:15 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 14:47 Robert Olsson
2003-12-10 23:05 ` David S. Miller
2003-12-12 23:10 ` Robert Olsson
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=16341.58771.558850.163216@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--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).