Le lundi 13 juin 2011 à 08:05 +1200, Richard Scobie a écrit :
> I have a server with a bonded quad 82571EB card, the kernel of which has 
> just been updated from 2.6.35.7 to 2.6.39.1.
> 
> Now, ifconfig shows dropped packets, but ethtool output shows nothing 
> untoward - I am assuming the ethtool output is the correct answer. What 
> does ifconfig count as dropped packets?
> 
> The latest Sourceforge e1000e driver gives the same result.
> 
> bond0     Link encap:Ethernet  HWaddr 00:15:17:75:E1:6D
>            inet addr:192.168.4.11  Bcast:192.168.4.255  Mask:255.255.255.0
>            inet6 addr: fe80::215:17ff:fe75:e16d/64 Scope:Link
>            UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
>            RX packets:15826566 errors:0 dropped:23685 overruns:0 frame:0
>            TX packets:13899764 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:0
>            RX bytes:11708531844 (10.9 GiB)  TX bytes:11753232178 (10.9 GiB)
> 
> bond1     Link encap:Ethernet  HWaddr 00:1B:21:87:4C:BC
>            inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
>            UP BROADCAST MASTER MULTICAST  MTU:9000  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:0
>            RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> 
> eth0      Link encap:Ethernet  HWaddr 00:15:17:75:E1:6D
>            UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
>            RX packets:2169872 errors:0 dropped:381 overruns:0 frame:0
>            TX packets:4319294 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:466283308 (444.6 MiB)  TX bytes:3789361885 (3.5 GiB)
>            Interrupt:17 Memory:d2220000-d2240000
> 
> eth1      Link encap:Ethernet  HWaddr 00:15:17:75:E1:6C
>            UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
>            RX packets:1740322 errors:0 dropped:4676 overruns:0 frame:0
>            TX packets:5533135 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:359511761 (342.8 MiB)  TX bytes:6115856972 (5.6 GiB)
>            Interrupt:16 Memory:d2260000-d2280000
> 
> eth2      Link encap:Ethernet  HWaddr 00:15:17:75:E1:6F
>            UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
>            RX packets:9784596 errors:0 dropped:4665 overruns:0 frame:0
>            TX packets:1617123 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:10433206012 (9.7 GiB)  TX bytes:297694172 (283.9 MiB)
>            Interrupt:18 Memory:d2320000-d2340000
> 
> eth3      Link encap:Ethernet  HWaddr 00:15:17:75:E1:6E
>            UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
>            RX packets:2131776 errors:0 dropped:4673 overruns:0 frame:0
>            TX packets:2430212 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:449530763 (428.7 MiB)  TX bytes:1550319149 (1.4 GiB)
>            Interrupt:17 Memory:d2360000-d2380000
> 
> ethtool -S eth1
> NIC statistics:
>       rx_packets: 1802523
>       tx_packets: 5578330
>       rx_bytes: 379706001
>       tx_bytes: 6133162132
>       rx_broadcast: 4717
>       tx_broadcast: 0
>       rx_multicast: 120
>       tx_multicast: 49
>       rx_errors: 0
>       tx_errors: 0
>       tx_dropped: 0
>       multicast: 120
>       collisions: 0
>       rx_length_errors: 0
>       rx_over_errors: 0
>       rx_crc_errors: 0
>       rx_frame_errors: 0
>       rx_no_buffer_count: 0
>       rx_missed_errors: 0
>       tx_aborted_errors: 0
>       tx_carrier_errors: 0
>       tx_fifo_errors: 0
>       tx_heartbeat_errors: 0
>       tx_window_errors: 0
>       tx_abort_late_coll: 0
>       tx_deferred_ok: 0
>       tx_single_coll_ok: 0
>       tx_multi_coll_ok: 0
>       tx_timeout_count: 0
>       tx_restart_queue: 0
>       rx_long_length_errors: 0
>       rx_short_length_errors: 0
>       rx_align_errors: 0
>       tx_tcp_seg_good: 181389
>       tx_tcp_seg_failed: 0
>       rx_flow_control_xon: 0
>       rx_flow_control_xoff: 0
>       tx_flow_control_xon: 0
>       tx_flow_control_xoff: 0
>       rx_long_byte_count: 379706001
>       rx_csum_offload_good: 1799082
>       rx_csum_offload_errors: 0
>       rx_header_split: 0
>       alloc_rx_buff_failed: 0
>       tx_smbus: 0
>       rx_smbus: 0
>       dropped_smbus: 0
>       rx_dma_failed: 0
>       tx_dma_failed: 0
> 

Literally dropped packet by the stack, because no protocol handler could
handle them.

In previous kernels (before 2.6.37), these packets were dropped too, but
no counter was incremented.

commit caf586e5f23cebb2a68cbaf288d59dbbf2d74052
Author: Eric Dumazet <[email protected]>
Date:   Thu Sep 30 21:06:55 2010 +0000

    net: add a core netdev->rx_dropped counter
    
    In various situations, a device provides a packet to our stack and we
    drop it before it enters protocol stack :
    - softnet backlog full (accounted in /proc/net/softnet_stat)
    - bad vlan tag (not accounted)
    - unknown/unregistered protocol (not accounted)
    
    We can handle a per-device counter of such dropped frames at core level,
    and automatically adds it to the device provided stats (rx_dropped), so
    that standard tools can be used (ifconfig, ip link, cat /proc/net/dev)
    
    This is a generalization of commit 8990f468a (net: rx_dropped
    accounting), thus reverting it.
    
    Signed-off-by: Eric Dumazet <[email protected]>
    Signed-off-by: David S. Miller <[email protected]>




------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to