All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: netdev@oss.sgi.com
Subject: how to get per-socket stats on udp rx buffer overflow?
Date: Thu, 23 May 2002 14:15:47 -0400	[thread overview]
Message-ID: <3CED31D3.B5892DF4@nortelnetworks.com> (raw)


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.

Thanks,

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

             reply	other threads:[~2002-05-23 18:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23 18:15 Chris Friesen [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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=3CED31D3.B5892DF4@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.