netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eli Cohen <eli@mellanox.co.il>
To: linux-net@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: receive errors
Date: Tue, 03 Jul 2007 18:39:20 +0300	[thread overview]
Message-ID: <1183477160.25031.170.camel@mtls03> (raw)

Hi,

I am running a benchmark that uses a UDP socket to send small packets
(20 bytes) from on side to the other side. I experience packet loss
reported by the benchmark and I can see that it matches what I see with
netstat:

[root@sw174 opt]# netstat -us
Udp:
    26971289 packets received
    7 packets to unknown port received.
    32615 packet receive errors
    155761284 packets sent

Can someone please direct to the source code that detects such receive
errors and/or suggest why such a thing could happen?

Thanks
Eli


                 reply	other threads:[~2007-07-03 16:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1183477160.25031.170.camel@mtls03 \
    --to=eli@mellanox.co.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).