From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: hannes@stressinduktion.org, bert.hubert@netherlabs.nl,
netdev@vger.kernel.org
Subject: Re: IPv6 routing table max_size badly dimensioned compared to IPv4
Date: Thu, 27 Feb 2014 17:47:55 -0500 (EST) [thread overview]
Message-ID: <20140227.174755.801004637112620140.davem@davemloft.net> (raw)
In-Reply-To: <1393534920.26794.40.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 27 Feb 2014 13:02:00 -0800
> On Thu, 2014-02-27 at 21:50 +0100, Hannes Frederic Sowa wrote:
>
>> We store those routes back into the routing table, so we must have a way to
>> count them and trigger gc at some point.
>
> Right, and current implementation will not scale.
>
> If we need to perform 10000 inserts per second, and gc timeout is 60
> seconds, tree contains 600.000 entries, gc takes forever...
The only long term solution is to align ipv6 to be more like ipv4.
What's interesting is that if you look at the code, the original
author clearly intended to make callers be able to use route's
from the tree as-is without cloning.
next prev parent reply other threads:[~2014-02-27 22:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 19:24 IPv6 routing table max_size badly dimensioned compared to IPv4 bert hubert
2014-02-27 19:59 ` Eric Dumazet
2014-02-27 20:05 ` bert hubert
2014-02-27 20:08 ` Hannes Frederic Sowa
2014-02-27 20:23 ` Eric Dumazet
2014-02-27 20:50 ` Hannes Frederic Sowa
2014-02-27 21:02 ` Eric Dumazet
2014-02-27 22:47 ` David Miller [this message]
2014-02-28 11:07 ` bert hubert
2014-04-04 16:03 ` Lukas Tribus
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=20140227.174755.801004637112620140.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bert.hubert@netherlabs.nl \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
/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).