All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "Rusty Russell" <rusty@rustcorp.com.au>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bne2 rx packet drop?
Date: Wed, 4 Aug 2010 16:47:03 -0700	[thread overview]
Message-ID: <1280965623.7554.33.camel@HP1> (raw)
In-Reply-To: <201008050859.57659.rusty@rustcorp.com.au>


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.
> 
> Any hints?  What are the conditions which cause mac_discard?
> 

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.



  reply	other threads:[~2010-08-04 23:48 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 [this message]
2010-08-19  2:35   ` Rusty Russell
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=1280965623.7554.33.camel@HP1 \
    --to=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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.