All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael Chan" <mchan@broadcom.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bne2 rx packet drop?
Date: Thu, 19 Aug 2010 12:05:34 +0930	[thread overview]
Message-ID: <201008191205.34696.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1280965623.7554.33.camel@HP1>

On Thu, 5 Aug 2010 09:17:03 am Michael Chan wrote:
> 
> On Wed, 2010-08-04 at 16:29 -0700, Rusty Russell wrote:
> > Hi Michael (and netdev!)
> > 
> >    I've got a customer seeing ~1000 rx packets dropped per day (on a busy
> > interface, bonding) via 'netstat -ni' RX-DRP's field across their 4-node
> > cluster.  The code seems to put checksum_discard and mac_discard into
> > that counter, so I'm not sure what the root cause is.
> 
> Please ask the customer for ethtool -S ethx.  It has a number of
> different counters for rx dropped packets so we can get a better idea of
> what's happening.

Thanks, finally got this.  Here's the ethtool -S from one of the quiet
interfaces:

NIC statistics:
    rx_bytes: 4490460
    rx_error_bytes: 0
    tx_bytes: 0
    tx_error_bytes: 0
    rx_ucast_packets: 0
    rx_mcast_packets: 0
    rx_bcast_packets: 31879
    tx_ucast_packets: 0
    tx_mcast_packets: 0
    tx_bcast_packets: 0
    tx_mac_errors: 0
    tx_carrier_errors: 0
    rx_crc_errors: 0
    rx_align_errors: 0
    tx_single_collisions: 0
    tx_multi_collisions: 0
    tx_deferred: 0
    tx_excess_collisions: 0
    tx_late_collisions: 0
    tx_total_collisions: 0
    rx_fragments: 0
    rx_jabbers: 0
    rx_undersize_packets: 0
    rx_oversize_packets: 0
    rx_64_byte_packets: 27241
    rx_65_to_127_byte_packets: 0
    rx_128_to_255_byte_packets: 0
    rx_256_to_511_byte_packets: 32
    rx_512_to_1023_byte_packets: 4606
    rx_1024_to_1522_byte_packets: 0
    rx_1523_to_9022_byte_packets: 0
    tx_64_byte_packets: 0
    tx_65_to_127_byte_packets: 0
    tx_128_to_255_byte_packets: 0
    tx_256_to_511_byte_packets: 0
    tx_512_to_1023_byte_packets: 0
    tx_1024_to_1522_byte_packets: 0
    tx_1523_to_9022_byte_packets: 0
    rx_xon_frames: 0
    rx_xoff_frames: 0
    tx_xon_frames: 0
    tx_xoff_frames: 0
    rx_mac_ctrl_frames: 0
    rx_filtered_packets: 4630821
    rx_discards: 0
    rx_fw_discards: 31876

Thanks!
Rusty.

  reply	other threads:[~2010-08-19  2:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 23:29 bne2 rx packet drop? Rusty Russell
2010-08-04 23:47 ` Michael Chan
2010-08-19  2:35   ` Rusty Russell [this message]
2010-08-05  0:08 ` Rusty Russell

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=201008191205.34696.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=mchan@broadcom.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.