From: Patrick McHardy <kaber@trash.net>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>,
patrick@tykepenguin.com
Subject: [NET 00/06]: Increase number of possible routing tables
Date: Thu, 10 Aug 2006 21:29:57 +0200 (MEST) [thread overview]
Message-ID: <20060810192957.14867.71965.sendpatchset@localhost.localdomain> (raw)
These are the updated patches (against net-2.6.19) to increase the number
of possible routing tables to 2^32. They basically consist of four parts:
- Use u32 for routing table IDs everywhere inside the kernel
- Introduce new netlink attributes to carry extended table IDs and add
compatibility functions to use either rtm_table or the new attributes
if given.
- Prepare IPv4/IPv6/DecNET for increasing RT_TABLE_MAX to 2^32 by using
hash tables instead of a fixed size array of pointers (IPv4 and DecNET,
IPv6 already contains that part) and replacing iterations over all
possible table IDs by hash walking.
- Finally, increase RT_TABLE_MAX to 2^32
IPv4 and IPv6 are tested with and without CONFIG_MULTIPLE_TABLES, DecNET
is only compile tested.
include/linux/fib_rules.h | 4 +
include/linux/rtnetlink.h | 12 ++-
include/net/dn_fib.h | 7 -
include/net/fib_rules.h | 7 +
include/net/ip6_route.h | 7 +
include/net/ip_fib.h | 39 +++-------
net/core/fib_rules.c | 5 -
net/decnet/dn_fib.c | 62 +---------------
net/decnet/dn_route.c | 1
net/decnet/dn_rules.c | 2
net/decnet/dn_table.c | 136 ++++++++++++++++++++++++++----------
net/ipv4/fib_frontend.c | 117 ++++++++++++++++++++-----------
net/ipv4/fib_hash.c | 30 ++++----
net/ipv4/fib_lookup.h | 4 -
net/ipv4/fib_rules.c | 7 +
net/ipv4/fib_semantics.c | 5 -
net/ipv4/fib_trie.c | 32 ++++----
net/ipv4/route.c | 1
net/ipv6/fib6_rules.c | 1
net/ipv6/ip6_fib.c | 171 ++++++++++++++++++++++++++++++++++++++++------
net/ipv6/route.c | 141 ++-----------------------------------
21 files changed, 430 insertions(+), 361 deletions(-)
Patrick McHardy:
[NET]: Use u32 for routing table IDs
[NET]: Introduce RTA_TABLE/FRA_TABLE attributes
[IPV4]: Increase number of possible routing tables to 2^32
[IPV6]: Increase number of possible routing tables to 2^32
[DECNET]: Increase number of possible routing tables to 2^32
[NET]: Increate RT_TABLE_MAX to 2^32
next reply other threads:[~2006-08-10 19:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 19:29 Patrick McHardy [this message]
2006-08-10 19:29 ` [NET 01/06]: Use u32 for routing table IDs Patrick McHardy
2006-08-11 6:08 ` David Miller
2006-08-10 19:30 ` [NET 02/06]: Introduce RTA_TABLE/FRA_TABLE attributes Patrick McHardy
2006-08-11 6:09 ` David Miller
2006-08-11 7:02 ` Michael Tokarev
2006-08-11 7:33 ` David Miller
2006-08-10 19:30 ` [IPV4 03/06]: Increase number of possible routing tables to 2^32 Patrick McHardy
2006-08-11 6:10 ` David Miller
2006-08-10 19:30 ` [IPV6 04/06]: " Patrick McHardy
2006-08-11 6:11 ` David Miller
2006-08-10 19:30 ` [DECNET 05/06]: " Patrick McHardy
2006-08-11 6:11 ` David Miller
2006-08-10 19:30 ` [NET 06/06]: Increate RT_TABLE_MAX " Patrick McHardy
2006-08-11 6:12 ` David Miller
2006-08-11 6:39 ` [NET 00/06]: Increase number of possible routing tables Michael Tokarev
2006-08-11 6:44 ` David Miller
2006-08-11 6:56 ` Michael Tokarev
2006-08-11 9:48 ` Thomas Graf
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=20060810192957.14867.71965.sendpatchset@localhost.localdomain \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=patrick@tykepenguin.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).