From: "Bob Falken" <NetFestivalHaveFun@gmx•com>
To: "Hannes Frederic Sowa" <hannes@stressinduktion•org>,
"Eric Dumazet" <eric.dumazet@gmail•com>
Cc: "Ben Greear" <greearb@candelatech•com>, netdev@vger•kernel.org
Subject: Re: Multicast routing stops functioning after 4G multicast packets recived.
Date: Sat, 21 Dec 2013 23:35:00 +0100 [thread overview]
Message-ID: <20131221223501.110860@gmx.com> (raw)
OK, so at the exact time that the incoming interface for multicast packet count reaches 2^32,
the /proc/net/ip_mr_cache stops updating.
after a while, one by one the multicast groups in ip_mr_cache disapperes, and after 227sec all of them are gone.
perf script net_dropmonitor:
-----------
# ========
# captured on: Sat Dec 21 23:27:37 2013
# ========
#
Starting trace (Ctrl-C to dump results)
Warning:
Processed 788648 events and lost 118 chunks!
Check IO/CPU overload!
Gathering kallsyms data
35200/35200
LOCATION OFFSET COUNT
_stext 18446744071578845580 6
_stext 18446744071578843536 785790
_stext 18446744071578843530 1
-------------
netstat -s:
Ip:
622406 total packets received
2 with invalid addresses
0 forwarded
0 incoming packets discarded
599574 incoming packets delivered
520762 requests sent out
8 dropped because of missing route
Icmp:
19361 ICMP messages received
0 input ICMP message failed.
ICMP input histogram:
echo requests: 8415
echo replies: 10946
19361 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
echo request: 10946
echo replies: 8415
IcmpMsg:
InType0: 10946
InType8: 8415
OutType0: 8415
OutType8: 10946
Tcp:
15 active connections openings
15 passive connection openings
0 failed connection attempts
0 connection resets received
29 connections established
477938 segments received
482321 segments send out
4 segments retransmited
0 bad segments received.
0 resets sent
Udp:
586 packets received
0 packets to unknown port received.
0 packet receive errors
649 packets sent
UdpLite:
TcpExt:
15862 delayed acks sent
Quick ack mode was activated 1 times
1 packets directly queued to recvmsg prequeue.
390374 packet headers predicted
1767 acknowledgments not containing data payload received
58169 predicted acknowledgments
4 congestion windows recovered without slow start after partial ack
4 other TCP timeouts
1 DSACKs sent for old packets
4 DSACKs received
TCPSackShiftFallback: 3
IpExt:
InNoRoutes: 1
InMcastPkts: 40015
OutMcastPkts: 18427
InBcastPkts: 80035
InOctets: 1116615859
OutOctets: 33742922
InMcastOctets: 1046924948
OutMcastOctets: 734556
InBcastOctets: 7255577
---------------------
----- Original Message -----
From: Hannes Frederic Sowa
Sent: 12/19/13 06:32 PM
To: Eric Dumazet
Subject: Re: Multicast routing stops functioning after 4G multicast packets recived.
On Thu, Dec 19, 2013 at 09:24:18AM -0800, Eric Dumazet wrote:
> On Thu, 2013-12-19 at 17:28 +0100, Bob Falken wrote:
> > The only reason why i give information about 2.6.36.4 is that its the
> > only latest kernel that was functioning properly.
> > i.e kernel >= 2.6.37 is not woking. so its a bisecting of the kernel
> > versions to help a coder see when/where the isse was implemented in
> > the kernel.
> >
> > I do not need a backport patch for an old kernel, I generally only
> > need the issue looked into and get fixed so that I dont have to use an
> > old kernel. :)
> >
> > I have no issue reproducing the issue on the recent kernels. however i
> > have not tried the GIT kernel.
> >
> > I restarted the server just a moment ago. i will install and run
> > dropwatch and provide feedback in about 17hours.
>
> You said that "cat /proc/net/ip_mr_cache" gives nothing at all after
> 2^32 packets ?
>
> Thats a bit scary ... maybe a 32bit refcnt overflow, because of some
> imbalance...
That's my thought, too. :/
The ipmr.c rcu conversion happend in 2.6.37.
next reply other threads:[~2013-12-21 22:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 22:35 Bob Falken [this message]
2014-01-03 7:37 ` Multicast routing stops functioning after 4G multicast packets recived Hannes Frederic Sowa
-- strict thread matches above, loose matches on Subject: below --
2014-01-12 0:25 Bob Falken
2014-01-09 20:14 Bob Falken
2014-01-10 6:36 ` Hannes Frederic Sowa
2014-01-10 7:01 ` Eric Dumazet
2014-01-10 7:10 ` Hannes Frederic Sowa
2014-01-10 7:32 ` Eric Dumazet
2014-01-10 7:43 ` Hannes Frederic Sowa
2014-01-10 7:50 ` Hannes Frederic Sowa
2014-01-12 7:42 ` Hannes Frederic Sowa
2014-01-13 0:56 ` Eric Dumazet
2014-01-07 17:01 Bob Falken
2014-01-07 17:43 ` Hannes Frederic Sowa
2014-01-07 20:11 ` Hannes Frederic Sowa
2014-01-07 20:20 ` Hannes Frederic Sowa
2014-01-07 20:26 ` Eric Dumazet
2014-01-07 20:29 ` Hannes Frederic Sowa
2014-01-04 18:53 Bob Falken
2013-12-19 16:28 Bob Falken
2013-12-19 17:24 ` Eric Dumazet
2013-12-19 17:32 ` Hannes Frederic Sowa
2013-12-22 3:10 ` Hannes Frederic Sowa
2013-12-19 14:48 Bob Falken
2013-12-19 15:09 ` Hannes Frederic Sowa
2013-12-19 15:15 ` Ben Greear
2013-12-19 15:48 ` Hannes Frederic Sowa
2014-01-04 19:55 ` Julian Anastasov
2014-01-04 23:38 ` Hannes Frederic Sowa
2014-01-05 8:56 ` Julian Anastasov
2014-01-05 10:41 ` Hannes Frederic Sowa
2014-01-05 19:12 ` Eric Dumazet
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=20131221223501.110860@gmx.com \
--to=netfestivalhavefun@gmx$(echo .)com \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=greearb@candelatech$(echo .)com \
--cc=hannes@stressinduktion$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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