From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 85091] New: neighbour table overflow is not reported and impacts localhost TCP connectivity
Date: Wed, 24 Sep 2014 09:32:16 -0700 [thread overview]
Message-ID: <20140924093216.083c77b4@urahara> (raw)
Begin forwarded message:
Date: Wed, 24 Sep 2014 03:44:41 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 85091] New: neighbour table overflow is not reported and impacts localhost TCP connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=85091
Bug ID: 85091
Summary: neighbour table overflow is not reported and impacts
localhost TCP connectivity
Product: Networking
Version: 2.5
Kernel Version: 3.8 - 3.17-rc6
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: aschultz@tpip.net
Regression: No
With the default gc_thresh values and a busy /16 network attached, the
neighbour cache can overflow. No indication is given that this happens and it
does impact TCP on localhost.
Test setup:
* about 16k (simulated IP/MAC's) on one interface
* web server behind on second interface
* routing between the two
* HTTP benchmark from the 16k IP's to the web server
* for localhost connectivity verification a netperf instance is run on
localhost like so: 'netperf -D 1 -l 600 127.0.0.1'
Result:
Kernel has to learn the 16k IP/MAC combinations, as soon as gc_thresh3 is hit,
netperf stalls, no syslog/kernel message indicates the problem.
The only indication are log entries like this:
"net_ratelimit: 1464 callbacks suppressed"
No other messages are logged.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-09-24 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 16:32 Stephen Hemminger [this message]
2014-09-24 19:11 ` Fw: [Bug 85091] New: neighbour table overflow is not reported and impacts localhost TCP connectivity Cong Wang
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=20140924093216.083c77b4@urahara \
--to=stephen@networkplumber.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