From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: eric.dumazet@gmail.com, fubar@us.ibm.com, andy@greyhouse.net
Subject: bonding inactive slaves vs rx_dropped
Date: Thu, 14 Feb 2013 16:06:57 -0500 (EST) [thread overview]
Message-ID: <20130214.160657.1394358701071068786.davem@davemloft.net> (raw)
People are starting to notice that rx_dropped now increments on every
packet received on an bond's inactive slave.
I'm actually fine with rx_dropped incrementing in this situation.
The problem I want to address is that rx_dropped is encompassing
several unrelated situations and thus has become less useful for
diagnosis.
I think we should add some new RX stats such that we can get at
least a small amount of granularity for rx_dropped.
This way team, bond, etc. can increment a new netdev_stats->rx_foo in
this situation, and then someone doing diagnosis can see that
rx_dropped and rx_foo are incrementing at similar rates.
next reply other threads:[~2013-02-14 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 21:06 David Miller [this message]
2013-02-14 21:51 ` bonding inactive slaves vs rx_dropped Jay Vosburgh
2013-02-14 22:18 ` David Miller
2013-02-14 23:43 ` Jay Vosburgh
2013-02-15 17:47 ` Ben Hutchings
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=20130214.160657.1394358701071068786.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=eric.dumazet@gmail.com \
--cc=fubar@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).