From: "David S. Miller" <davem@redhat.com>
To: greearb@candelatech.com
Cc: mark@mark.mielke.cc, cfriesen@nortelnetworks.com,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: RFC: per-socket statistics on received/dropped packets
Date: Sun, 09 Jun 2002 21:34:40 -0700 (PDT) [thread overview]
Message-ID: <20020609.213440.04716391.davem@redhat.com> (raw)
In-Reply-To: <3D039D22.2010805@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
Date: Sun, 09 Jun 2002 11:23:30 -0700
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.
Why can't you just disable the other UDP services, and then there is
no question which UDP server/client is causing the drops.
Every argument I hear is one out of lazyness. And that is not a
reason to add something. Simply put, I don't want to add all of this
per-socket counter bumping that only, at best, 1 tenth of 1 percent
of people will use. This means that the rest of the world eats the
overhead just for this small group that actually uses it.
next prev parent reply other threads:[~2002-06-10 4:38 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 19:37 RFC: per-socket statistics on received/dropped packets Chris Friesen
2002-06-07 3:21 ` David S. Miller
2002-06-07 15:34 ` Chris Friesen
2002-06-07 22:15 ` Ben Greear
2002-06-08 21:05 ` Mark Mielke
2002-06-08 23:04 ` David S. Miller
2002-06-09 0:13 ` Ben Greear
2002-06-09 0:51 ` David S. Miller
2002-06-09 18:23 ` Ben Greear
2002-06-10 4:34 ` David S. Miller [this message]
2002-06-10 5:55 ` Mark Mielke
2002-06-10 6:08 ` Ben Greear
2002-06-10 12:03 ` Lincoln Dale
2002-06-10 12:18 ` David S. Miller
2002-06-10 12:24 ` jamal
2002-06-10 13:57 ` Mark Mielke
2002-06-10 14:45 ` jamal
2002-06-10 14:56 ` jamal
2002-06-10 19:28 ` Chris Friesen
2002-06-10 18:44 ` David Ford
2002-06-10 18:50 ` Thunder from the hill
2002-06-10 19:02 ` David Ford
2002-06-11 22:41 ` Bill Davidsen
2002-06-12 3:41 ` David S. Miller
2002-06-12 3:57 ` Richard Guy Briggs
2002-06-12 5:20 ` Mark Mielke
2002-06-12 6:08 ` Pekka Savola
2002-06-12 6:26 ` Ben Greear
2002-06-12 6:32 ` Pekka Savola
2002-06-12 6:49 ` Ben Greear
2002-06-12 12:11 ` Horst von Brand
2002-06-12 12:28 ` Lincoln Dale
2002-06-12 12:33 ` jamal
2002-06-12 12:44 ` Lincoln Dale
2002-06-12 13:00 ` jamal
2002-06-12 14:53 ` Mark Mielke
2002-06-12 15:57 ` jamal
2002-06-12 17:00 ` Horst von Brand
2002-06-14 0:24 ` Lincoln Dale
2002-06-14 15:51 ` Stephen Hemminger
2002-06-14 18:09 ` Ben Greear
2002-06-12 14:52 ` john slee
2002-06-12 14:55 ` Mark Mielke
2002-06-13 2:52 ` Lincoln Dale
2002-06-13 19:53 ` Horst von Brand
2002-06-13 7:21 ` David Schwartz
2002-06-13 8:44 ` Lincoln Dale
2002-06-13 10:10 ` David Schwartz
2002-06-23 2:03 ` Alan Cox
2002-06-23 2:05 ` Lincoln Dale
2002-06-12 9:18 ` Sean Hunter
2002-06-09 14:47 ` Pekka Pietikäinen
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=20020609.213440.04716391.davem@redhat.com \
--to=davem@redhat.com \
--cc=cfriesen@nortelnetworks.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mark.mielke.cc \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox