From: Ben Greear <greearb@candelatech.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Simon Chen <simonchennj@gmail.com>, netdev@vger.kernel.org
Subject: Re: increase the number of routing tables
Date: Sat, 28 Jan 2012 18:46:01 -0800 [thread overview]
Message-ID: <4F24B2E9.3010600@candelatech.com> (raw)
In-Reply-To: <1327804887.2805.20.camel@edumazet-laptop>
On 01/28/2012 06:41 PM, Eric Dumazet wrote:
> Le samedi 28 janvier 2012 à 21:20 -0500, Simon Chen a écrit :
>> Hey folks,
>>
>> To my limited knowledge, Linux currently supports 256 (255?) routing
>> tables defined in /etc/iproute2/rt_tables.
>>
>> Is there a way to increase this number to something much larger? Are
>> there performance/scalability concerns there? I am trying to have
>> customized routing table for each IP address (using "ip rule add from
>> xxx table yyy"). I am not sure exactly how many IPs I'll handle, but
>> certainly more than 255...
>>
>
> Its is possible, but probably not scalable.
I've run with a few thousand routing tables and probably 5000 or so
rules. It seems to run OK....
> You really should not have too many "ip rule" entries, since they are
> evaluated linearly.
For every packet, or maybe just until conn-track gets an entry
for the connection?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-01-29 2:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 2:20 increase the number of routing tables Simon Chen
2012-01-29 2:41 ` Eric Dumazet
2012-01-29 2:46 ` Ben Greear [this message]
2012-01-29 4:20 ` Simon Chen
2012-01-29 19:26 ` Ben Greear
2012-01-31 3:06 ` Simon Chen
2012-01-29 21:02 ` David Miller
2012-01-29 21:01 ` David Miller
2012-01-30 17:26 ` Ben Greear
2012-01-30 17:36 ` David Miller
2012-01-30 12:25 ` Thomas Graf
2012-01-30 12:44 ` Eric Dumazet
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=4F24B2E9.3010600@candelatech.com \
--to=greearb@candelatech.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=simonchennj@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 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).