lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 30 Aug 2009 09:51:55 +0930
From:	Mark Smith <lk-netdev@...netdev.nosense.org>
To:	David Miller <davem@...emloft.net>
Cc:	cl@...ux-foundation.org, sri@...ibm.com, dlstevens@...ibm.com,
	eric.dumazet@...il.com, netdev@...r.kernel.org,
	niv@...ux.vnet.ibm.com
Subject: Re: UDP multicast packet loss not reported if TX ring overrun?

On Fri, 28 Aug 2009 12:24:59 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:

> From: Christoph Lameter <cl@...ux-foundation.org>
> Date: Fri, 28 Aug 2009 09:53:40 -0400 (EDT)
> 
> > Seems though that the qdisc drop count does not flow into the tx_dropped
> > counter for the interface.
> 
> And it should not.
> 
> The qdisc drops the packet due to flow control, not the hardware
> device.
> 
> Device drops are for things like transmission errors on the wire.
> 
> If you start incrementing tx_dropped here, people won't be able
> to tell they have a deteriorating cable or bad switch or similar.

And it does, because Cisco do it this way, although they record them as
TX errors not drops. It's quite annoying to have to keep reminding
yourself that the errors shown on the traffic graphs probably aren't
actually errors - of course real errors then become hidden in the
"normal" ones.

> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ