Vishal, As in this page (I assume you're referring to same text) http://www.informit.com/articles/article.aspx?p=174309&seqNum=3, rx_overflow and other stats are "ge" interface specific. Some drivers can use a different name for the same statistics; and you don't find any such statistics in remaining drivers. Some of the stats are available in all drivers.. like Ipkts, Ipkts64, Ibytes, Ibytes64, Opkts, Opkts64, Obytes, Obytes64, Ierr, Oerr, etc.
Gireesh ---- From: Vishal Ahuja [mailto:[email protected]] Sent: Tuesday, April 13, 2010 4:11 AM To: Gireesh Nagabhushana Cc: [email protected] Subject: Re: [networking-discuss] Packet drops (NIC buffer overflow, protocol processing) Hi Gireesh, Thanks for that. I did run kstat, but I am not sure why the following are not reported: 1. rx_overflow counter: Number of times the hardware is unable to receive a packet due to the internal FIFOs being full. 2. no_tmds counter: Number of times transmit packets are posted on the driver streams queue for processing later by the queues service routine. 3. nocanput counter: Number of times a packet is simply dropped by the driver because the module above the driver cannot accept the packet. I found these in "Maximizing Performance of a Gigabit Ethernet NIC Interface" by Francesco DiMambro, Sun Microsystems, Inc. These are the numbers that I am looking for, but kstat's output doesn't have these. Is there a reason? Thank you, Vishal On Mon, Apr 12, 2010 at 3:28 PM, Gireesh Nagabhushana <[email protected]> wrote: netstat can show the number of frames received/sent (Ipkts/Opkts), received/sent with error (Ierrs/Oerrs), etc. But you may get more detailed stats with kstat. If interface is e1000g0, try "kstat -m e1000g -i 0". Similarly for Realtek interface you can get its statistics using kstat. To understand what each entry in kstat is for, you can go through the driver source. Gireesh From: [email protected] [mailto:[email protected]] On Behalf Of Vishal Ahuja Sent: Tuesday, April 13, 2010 2:56 AM To: [email protected] Subject: [networking-discuss] Packet drops (NIC buffer overflow, protocol processing) Hi All, I am running some experiments for which I need to figure out where the packets are being lost at the receiver. The network protocol is UDP, and my machine has a realtek driver. Is there a way to pin point the number of packets lost at the NIC, and how many in the kernel. I need to do it for another machine which has the e1000g driver for the NIC. Is netstat able to capture this, or dtrace? Thank you, Vish _______________________________________________ networking-discuss mailing list [email protected]
