From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: net: add a core netdev->tx_dropped counter
Date: Fri, 28 Mar 2014 16:51:07 -0400 (EDT) [thread overview]
Message-ID: <20140328.165107.2032068536221746348.davem@davemloft.net> (raw)
In-Reply-To: <1395935156.12610.295.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 27 Mar 2014 08:45:56 -0700
> From: Eric Dumazet <edumazet@google.com>
>
> Dropping packets in __dev_queue_xmit() when transmit queue
> is stopped (NIC TX ring buffer full or BQL limit reached) currently
> outputs a syslog message.
>
> It would be better to get a precise count of such events available in
> netdevice stats so that monitoring tools can have a clue.
>
> This extends the work done in caf586e5f23ce
> ("net: add a core netdev->rx_dropped counter")
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Applied, thanks Eric.
prev parent reply other threads:[~2014-03-28 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 15:45 [PATCH net-next] net: net: add a core netdev->tx_dropped counter Eric Dumazet
2014-03-28 20:51 ` David Miller [this message]
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=20140328.165107.2032068536221746348.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.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).