From: David Miller <davem@davemloft.net>
To: shemminger@osdl.org
Cc: peter.hicks@poggs.co.uk, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Thousands of interfaces
Date: Tue, 31 Oct 2006 13:36:39 -0800 (PST) [thread overview]
Message-ID: <20061031.133639.112620851.davem@davemloft.net> (raw)
In-Reply-To: <20061031102222.7ab1ed6b@freekitty>
From: Stephen Hemminger <shemminger@osdl.org>
Date: Tue, 31 Oct 2006 10:22:22 -0800
> On Tue, 31 Oct 2006 01:31:54 -0800 (PST)
> David Miller <davem@davemloft.net> wrote:
>
> > From: Peter Hicks <peter.hicks@poggs.co.uk>
> > Date: Tue, 31 Oct 2006 09:25:50 +0000
> >
> > [ Discussion belongs on netdev@vger.kernel.org, added to CC: ]
> >
> > > I have a dual 3GHz Xeon machine with a 2.4.21 kernel and thousands (15k+) of
> > > ipip tunnel interfaces. These are being used to tunnel traffic from remote
> > > routers, over a private network, and handed off to a third party.
> > ...
> > > Is it possible to speed up creation of the interfaces? Currently it takes
> > > around 24 hours. Is there are more efficient way to handle a very large
> > > number of IP-IP tunnels? Would upgrading to a 2.6 kernel be of use?
> >
>
>
> 2.4 has a several N^2 searches for interfaces (and is in deep freeze by now).
> 2.6 had several changes to handle 1000's of interfaces.
Oops I didn't notice this was with 2.4.x. Indeed, 2.4.x definitely
cannot handle large numbers of networking interfaces at all without
major surgery. 2.6.x should handle this significantly better.
next prev parent reply other threads:[~2006-10-31 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 9:25 Peter Hicks
2006-10-31 9:31 ` David Miller
2006-10-31 15:55 ` Ben Greear
2006-10-31 18:22 ` Stephen Hemminger
2006-10-31 21:36 ` David Miller [this message]
2006-10-31 18:46 ` Michael Tokarev
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=20061031.133639.112620851.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.hicks@poggs.co.uk \
--cc=shemminger@osdl.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
all inboxes | Powered by JetHome®