netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: rvsjoen@gmail.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: NAPI enabled driver (tg3) silent packet loss ?
Date: Thu, 09 Oct 2008 11:47:09 -0700 (PDT)	[thread overview]
Message-ID: <20081009.114709.102722304.davem@davemloft.net> (raw)
In-Reply-To: <efa8e58e0810091053s4b1d25b7u621ee92be84d2041@mail.gmail.com>

From: "Rune V. Sjøen" <rvsjoen@gmail.com>
Date: Thu, 9 Oct 2008 19:53:45 +0200

[ netdev@vger.kernel.org is the place to discuss networking
  things ]

> I am sending frames to a host using, all the frames are accounted for
> in the rx_ucast_packets counter of the device.
> However the application shows a substantial packet loss. I assume that
> the rx_ucast_packets counter is incremented when the frame is received
> and then it is put into the ring buffer. I am having a hard time
> figuring out where these packets are lost, and my suspicion lies with
> the NAPI enabled tg3.
> 
> If the ring buffer overflows will the driver overwrite/drop packets
> without incrementing any counters ? That would explain why the packets
> are counted as received and then lost (by not being passed to the next
> layer).

No, the generic device dropped counter will increment, or the
device specific RX ring full condition will be indicated.

You can also check if the networking stack itself is dropping
the packet, using netstat -s and friends.

           reply	other threads:[~2008-10-09 18:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <efa8e58e0810091053s4b1d25b7u621ee92be84d2041@mail.gmail.com>]

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=20081009.114709.102722304.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rvsjoen@gmail.com \
    /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).