From: David Miller <davem@redhat.com>
To: David.Laight@ACULAB.COM
Cc: netdev@vger.kernel.org
Subject: Re: rx_dropped count for USB ethernet interfaces
Date: Thu, 26 Sep 2013 13:21:25 -0400 (EDT) [thread overview]
Message-ID: <20130926.132125.1343558938307288175.davem@redhat.com> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B735E@saturn3.aculab.com>
From: "David Laight" <David.Laight@ACULAB.COM>
Date: Thu, 26 Sep 2013 10:32:24 +0100
> It isn't exactly useful behaviour though.
In your opinion.
We have tracepoints for people who want more fine grained drops
in these kinds of situations.
Also, the behavior of this statistic has existed for more than a
decade so changing it is really not in the cards. Therefore any
discussion about what would have been the best samentic to choose from
the beginning is moot.
next prev parent reply other threads:[~2013-09-26 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 16:22 rx_dropped count for USB ethernet interfaces David Laight
2013-09-25 18:46 ` David Miller
2013-09-26 9:32 ` David Laight
2013-09-26 17:21 ` David Miller [this message]
2013-09-27 8:39 ` David Laight
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=20130926.132125.1343558938307288175.davem@redhat.com \
--to=davem@redhat.com \
--cc=David.Laight@ACULAB.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).