public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mru@kth.se (Måns Rullgård)
To: KyoungSoo Park <kyoungso@cs.princeton.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to detect udp packets drops ?
Date: Wed, 10 Mar 2004 22:20:53 +0100	[thread overview]
Message-ID: <yw1xoer4xutm.fsf@kth.se> (raw)
In-Reply-To: <404F855E.9090009@cs.princeton.edu> (KyoungSoo Park's message of "Wed, 10 Mar 2004 16:15:10 -0500")

KyoungSoo Park <kyoungso@cs.princeton.edu> writes:

> Thank you for your kind response.  But, if I follow your test
> senario, I cannot know which entity drops the packets.  Routers on
> the path also can get congested and may drop the packets.

That is true.

> What I really want is to know is if the "kernel"(whch is supposed to
> receive packets) drops packets.

Do you mean you want to know if the kernel's receive buffer overflows?
That could be possible in theory, but I don't know whether it's
possible with the current Linux kernels.

> Also I don't want to contribute to the congestion by sending test UDP
> packets, because that may worsen the situation.
> Isn't there any way to monitor the packet drops at the end host by
> just looking at the "packet drop counter"?

If the packet reaches the end host the only reason for dropping it
would be a filled receive buffer.  The size of the buffer can be set
using setsockopt().

-- 
Måns Rullgård
mru@kth.se

      parent reply	other threads:[~2004-03-10 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 21:28 Read-only bind mounts - will they be included in 2.4.x kernel? Frank Myhr
2004-03-10 19:41 ` how to detect udp packets drops ? KyoungSoo Park
2004-03-10 20:51   ` Måns Rullgård
     [not found]     ` <404F855E.9090009@cs.princeton.edu>
2004-03-10 21:20       ` Måns Rullgård [this message]

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=yw1xoer4xutm.fsf@kth.se \
    --to=mru@kth.se \
    --cc=kyoungso@cs.princeton.edu \
    --cc=linux-kernel@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