From: Ulrich Weber <uweber@astaro.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC PATCH] dont create cached routes from ARP requests
Date: Thu, 23 Sep 2010 16:47:08 +0200 [thread overview]
Message-ID: <20100923144708.GA8037@babylon> (raw)
In-Reply-To: <20100922.203442.233700254.davem@davemloft.net>
On Wed, Sep 22, 2010 at 08:34:42PM -0700, David Miller wrote:
> From: Ulrich Weber <uweber@astaro.com>
> Date: Wed, 22 Sep 2010 18:22:09 +0200
>
> > Background: At home I have two Internet connections, DSL and Cable.
> > DSL is the primary uplink while Cable is the secondary.
> > My Cable ISP is flooding me with ARP request from 10.0.0.0/8,
> > which creates routes via the primary uplink.
> > There are thousands of cached routes and after some time
> > I get "Neighbour table overflow" messages.
>
> If you get neighbour table overflows, something is holding a reference
> to the routing cache entry and/or the neighbour entries those routing
> cache entries are attached to.
>
> If these really are transient entries, they should be trivially
> garbage collected and not cause any problems at all.
rt_garbage_collect is not called within rt_intern_hash,
because the call is done within softirq context.
Forcing the call of rt_garbage_collect didn't help either,
there are no routes freed afterwards...
Cheers
Ulrich
next prev parent reply other threads:[~2010-09-23 14:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 16:22 [RFC PATCH] dont create cached routes from ARP requests Ulrich Weber
2010-09-23 3:34 ` David Miller
2010-09-23 14:47 ` Ulrich Weber [this message]
2010-09-23 15:05 ` Eric Dumazet
2010-09-24 15:00 ` Ulrich Weber
2010-09-24 15:28 ` Eric Dumazet
2010-09-24 15:34 ` Eric Dumazet
2010-09-24 15:43 ` Ulrich Weber
2010-09-24 15:38 ` Ulrich Weber
2010-09-24 16:05 ` Eric Dumazet
2010-09-24 16:40 ` Ulrich Weber
2010-09-24 16:58 ` Eric Dumazet
2010-09-27 13:11 ` Ulrich Weber
2010-09-23 19:04 ` David 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=20100923144708.GA8037@babylon \
--to=uweber@astaro.com \
--cc=davem@davemloft.net \
--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).