From: Ben Greear <greearb@candelatech•com>
To: David Miller <davem@davemloft•net>
Cc: eric.dumazet@gmail•com, simonchennj@gmail•com, netdev@vger•kernel.org
Subject: Re: increase the number of routing tables
Date: Mon, 30 Jan 2012 09:26:25 -0800 [thread overview]
Message-ID: <4F26D2C1.7030108@candelatech.com> (raw)
In-Reply-To: <20120129.160152.1463516627658543873.davem@davemloft.net>
On 01/29/2012 01:01 PM, David Miller wrote:
> From: Ben Greear<greearb@candelatech•com>
> Date: Sat, 28 Jan 2012 18:46:01 -0800
>
>> On 01/28/2012 06:41 PM, Eric Dumazet wrote:
>>> 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?
>
> When the routing cache is removed, using a huge number of rules is not
> going to be something you want to do any more because the rule table
> will be inspected on every route lookup.
Well, that sounds like a reason to keep the routing cache around,
even if it isn't used by default, perhaps.
Thanks,
Ben
--
Ben Greear <greearb@candelatech•com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-01-30 17:26 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
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 [this message]
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=4F26D2C1.7030108@candelatech.com \
--to=greearb@candelatech$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=simonchennj@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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