From: Andre Tomt <andre@tomt.net>
To: Harald Welte <laforge@gnumonks.org>
Cc: Linux Netdev List <netdev@oss.sgi.com>
Subject: Re: [PATCH + RFC] neighbour/ARP cache scalability
Date: Tue, 21 Sep 2004 09:04:18 +0200 [thread overview]
Message-ID: <414FD272.6010309@tomt.net> (raw)
In-Reply-To: <20040920225140.GH1307@sunbeam.de.gnumonks.org>
Harald Welte wrote:
> As a result, on systems with large networks (think of even less than 16
> bit netmasks!) the neighbour table can grow quite significantly,
> especially if some jerk runs pktgen with random destinations, and we
> start expiring 'real' neighbours in favour of incomplete ones.
Or just regular worms/viruses traversing the Internet. Usually in setups
I've seen, the arp cache overflows within seconds even on "smaller"
prefixes like /21. The networks did get redesigned properly as a result
of this however.
next prev parent reply other threads:[~2004-09-21 7:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 22:51 [PATCH + RFC] neighbour/ARP cache scalability Harald Welte
2004-09-21 6:29 ` David S. Miller
2004-09-21 7:04 ` Andre Tomt [this message]
2004-09-21 7:37 ` Robert Olsson
2004-09-21 8:58 ` Andi Kleen
2004-09-21 11:19 ` Pekka Savola
2004-09-21 13:49 ` Harald Welte
2004-09-21 14:10 ` Pekka Savola
2004-09-21 15:14 ` YOSHIFUJI Hideaki / 吉藤英明
2004-09-21 15:36 ` Robert Olsson
2004-09-21 15:59 ` YOSHIFUJI Hideaki / 吉藤英明
2004-09-21 15:58 ` Pekka Savola
2004-09-21 16:04 ` YOSHIFUJI Hideaki / 吉藤英明
2004-09-21 16:39 ` Tim Gardner
2004-09-21 17:31 ` Andi Kleen
2004-09-21 17:58 ` Tim Gardner
2004-09-21 18:15 ` Andi Kleen
2004-09-21 20:34 ` Harald Welte
2004-09-21 20:58 ` Tim Gardner
2004-09-22 1:14 ` Harald Welte
2004-09-22 3:31 ` David S. Miller
2004-09-22 11:14 ` Harald Welte
2004-09-24 5:53 ` David S. Miller
2004-09-24 7:14 ` Glen Turner
2004-09-24 5:47 ` David S. Miller
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=414FD272.6010309@tomt.net \
--to=andre@tomt.net \
--cc=laforge@gnumonks.org \
--cc=netdev@oss.sgi.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).