Re: [PATCH] udp: sk_drops handling

[Wang Chen <wangchen@cn.fujitsu.com>]

Eric Dumazet said the following on 2008-6-18 5:31:
> In commits 33c732c36169d7022ad7d6eb474b0c9be43a2dc1 ([IPV4]: Add raw drops
> counter) and a92aa318b4b369091fd80433c80e62838db8bc1c ([IPV4]: Add raw
> drops
> counter),
> Wang Chen added raw drops counter for /proc/net/raw & /proc/net/raw6
> 
> This patch adds this capability to UDP sockets too (/proc/net/udp &
> /proc/net/udp6).
> 
> This means that 'RcvbufErrors' errors found in /proc/net/snmp can be also
> be examined for each udp socket.
> 
> # grep Udp: /proc/net/snmp
> Udp: InDatagrams NoPorts InErrors OutDatagrams RcvbufErrors SndbufErrors
> Udp: 23971006 75 899420 16390693 146348 0
> 
> # cat /proc/net/udp
>  sl  local_address rem_address   st tx_queue rx_queue tr tm->when
> retrnsmt  ---
> uid  timeout inode ref pointer drops
>  75: 00000000:02CB 00000000:0000 07 00000000:00000000 00:00000000
> 00000000  ---
>   0        0 2358 2 ffff81082a538c80 0
> 111: 00000000:006F 00000000:0000 07 00000000:00000000 00:00000000
> 00000000  ---
>   0        0 2286 2 ffff81042dd35c80 146348
> 
> In this example, only port 111 (0x006F) was flooded by messages that
> user program
> could not read fast enough. 146348 messages were lost.
> 

How about other place, such as, rxrpc_data_ready() also inc UDP_MIB_INERRORS.