netdev - Re: [net-next-2.6 PATCH 3/4] igb: Record host memory receive overflow in net

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]

Message-Id: <20090526.203624.32809185.davem@davemloft.net>
Date:	Tue, 26 May 2009 20:36:24 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jeffrey.t.kirsher@...el.com
Cc:	netdev@...r.kernel.org, hawk@...x.dk
Subject: Re: [net-next-2.6 PATCH 3/4] igb: Record host memory receive
 overflow in net_stats

From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Date: Tue, 26 May 2009 16:50:48 -0700

> Based on previous patch from Jesper Dangaard Brouer.
> 
> The RNBC (Receive No Buffers Count) register for the 82576, indicate
> that frames were received when there were no available buffers in host
> memory to store those frames (receive descriptor head and tail
> pointers were equal).  The packet is still received by the NIC if
> there is space in the FIFO on the NIC.
> 
> As the RNBC value is not a packet drop, the driver stores this value
> in net_stats.rx_fifo_errors to indicate that there were no system
> buffers available for the incoming packet.  Actual dropped packets
> are counted in the MPC value.
> 
> Saving the stats in dev->net_stats makes it visible via
> /proc/net/dev as "fifo", and thus viewable to ifconfig
> as "overruns" and 'netstat -i' as "RX-OVR".
> 
> The Receive No Buffers Count (RNBC) can already be queried by
> ethtool -S as "rx_no_buffer_count".
> 
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>

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