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] [day] [month] [year] [list]
Message-ID: <1353435943.2590.25.camel@edumazet-glaptop>
Date:	Tue, 20 Nov 2012 10:25:43 -0800
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Jon Schipp <jonschipp@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: /proc/net/softnet_stat & NAPI

On Tue, 2012-11-20 at 13:06 -0500, Jon Schipp wrote:
> In relation to packet drops, assuming a new kernel, NAPI driver, and
> no use of receive packet steering,
> does /proc/net/softnet_stats provide any useful packet drop information?
> 

no

> I know that on earlier 2.4 kernels one could grab the drops in the
> backlog queue from 2nd column in /proc/net/softnet_stats.
> In a modern systems that use NAPI, does softnet_stats serve a similar
> purpose e.g. display drops in a NAPI poll queue?

Second column is number of dropped packets because
one (percpu) queue reached netdev_max_backlog

But its only in the case packet must be queued in the first place.

With a NAPI driver and no RPS/RFS, packets wont be dropped here, as NAPI
netif_receive_skb() directly calls the network stack.

If frames are dropped, they should be dropped by the NIC itself.

Even with 2.4 kernels or non NAPI driver, you could have drops at NIC
level.


--
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