[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <8545971aec0612a0bca2801107d9493b.squirrel@imap.coplanar.net>
Date: Tue, 26 Oct 2010 15:53:27 -0400
From: "Jeremy Jackson" <jerj@...lanar.net>
To: netdev@...r.kernel.org
Subject: Unwanted aliasing of UDP checksum failed error counter
Trying to find source of packet loss on an 8node compute cluster, we find:
(not in this example, but on the real cluster)
in /proc/sys/net/snmp
Udp: InDatagrams NoPorts InErrors OutDatagrams RcvbufErrors SndbufErrors
Udp: 976460 1750 0 986795 0 0
InErrors *and* RcvbufErrors both go up with full socket buffer, this has
made troubleshooting our application more difficult. We were chasing UDP
checksum problems, until we checked linux source code, and found aliasing.
Is this done for assembly code efficiency? Any reason ENOMEM (ie socket
buffer full) can't avoid aliasing to UDP checksum failed errors?
in linux-source-2.6.32/net/ipv4/udp.c:__udp_queue_rcv_skb()
....
/* Note that an ENOMEM error is charged twice */
if (rc == -ENOMEM) {
UDP_INC_STATS_BH(sock_net(sk), UDP_MIB_RCVBUFERRORS,
is_udplite);
atomic_inc(&sk->sk_drops);
}
goto drop;
...
drop:
UDP_INC_STATS_BH(sock_net(sk), UDP_MIB_INERRORS, is_udplite);
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists