| To: | "David S. Miller" <davem@xxxxxxxxxx> |
|---|---|
| Subject: | Re: RFC: per-socket statistics on received/dropped packets |
| From: | Ben Greear <greearb@xxxxxxxxxxxxxxx> |
| Date: | Sun, 09 Jun 2002 11:23:30 -0700 |
| Cc: | mark@xxxxxxxxxxxxxx, cfriesen@xxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| Organization: | Candela Technologies |
| References: | <20020608170511.B26821@xxxxxxxxxxxxxx> <20020608.160407.101346167.davem@xxxxxxxxxx> <3D029DAF.5040006@xxxxxxxxxxxxxxx> <20020608.175108.84748597.davem@xxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 |
David S. Miller wrote: From: Ben Greear <greearb@xxxxxxxxxxxxxxx> Date: Sat, 08 Jun 2002 17:13:35 -0700If you're talking per-socket SNMP counters, then that could work.General protocol-wide counters would not help much, at least in my case. Why not? If you know where the drops are occurring, what else do you need to know? I need to account for packets on a per-session basis, where a session endpoint is a UDP port. So, knowing global protocol numbers is good, but it is not very useful for the detailed accounting I need. I could also use per-socket TCP counters, like re-transmits, etc. I have not looked to see if they are already there or not... Thanks, Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> <Ben_Greear AT excite.com> President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear |
| Previous by Date: | Network oops, george anzinger |
|---|---|
| Next by Date: | Re: Network oops, David S. Miller |
| Previous by Thread: | Re: RFC: per-socket statistics on received/dropped packets, David S. Miller |
| Next by Thread: | Re: RFC: per-socket statistics on received/dropped packets, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |