public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: cfriesen@nortelnetworks.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to get per-socket stats on udp rx buffer overflow?
Date: Fri, 24 May 2002 13:54:53 -0700 (PDT)	[thread overview]
Message-ID: <20020524.135453.115381323.davem@redhat.com> (raw)
In-Reply-To: <3CEEA9BA.AAFED19F@nortelnetworks.com>

   From: Chris Friesen <cfriesen@nortelnetworks.com>
   Date: Fri, 24 May 2002 16:59:38 -0400

   Is there any way for me to see how many incoming packets were dropped on a udp
   socket due to overflowing the input buffer?  I specifically want this
   information on a per-socket basis.

Available as global SNMP mib statistic, not available per-socket.

  reply	other threads:[~2002-05-24 21:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-24 20:59 how to get per-socket stats on udp rx buffer overflow? Chris Friesen
2002-05-24 20:54 ` David S. Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-25  2:59 Nivedita Singhvi
2002-05-28 20:52 ` Ben Greear
2002-05-29 13:58   ` Nivedita Singhvi
2002-05-29 15:30     ` Ben Greear
2002-05-29 18:59       ` Nivedita Singhvi

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=20020524.135453.115381323.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=cfriesen@nortelnetworks.com \
    --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