public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: cfriesen@nortelnetworks.com, linux-kernel@vger.kernel.org
Subject: Re: how to get per-socket stats on udp rx buffer overflow?
Date: Tue, 28 May 2002 13:52:58 -0700	[thread overview]
Message-ID: <3CF3EE2A.1030605@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205241949360.2424-100000@w-nivedita2.des.beaverton.ibm.com>



Nivedita Singhvi wrote:

>>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.
>>
> 
> The /proc/net/snmp Udp counter InErrors includes the global
> count. It would be expensive and usually unnecessary to keep
> per-socket stats. Is there a real need for seeing the 
> per-socket count?


It would not be that expensive..it's just an extra counter that
is bumped whenever a pkt is dropped.

I have need of similar information, but it's low priority
for me right now, so I probably won't be adding a patch anytime
soon...

 
> If it helps, you can check the current bytes in the recv queue
> in netstat output - you wont know how many bytes have been dropped,
> but at least you know the amnt in the queue waiting to be read..


That is nearly worthless unless you are really killing your machine
and constantly have your buffers full...

Ben


> 
> 
>>Chris
>>
> 
> thanks,
> Nivedita
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 


-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



  reply	other threads:[~2002-05-28 20:56 UTC|newest]

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

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=3CF3EE2A.1030605@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niv@us.ibm.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