From: Mark Mielke <mark@mark.mielke.cc>
To: Ben Greear <greearb@candelatech.com>
Cc: "David S. Miller" <davem@redhat.com>,
cfriesen@nortelnetworks.com, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: RFC: per-socket statistics on received/dropped packets
Date: Sat, 8 Jun 2002 17:05:11 -0400 [thread overview]
Message-ID: <20020608170511.B26821@mark.mielke.cc> (raw)
In-Reply-To: <3CFFB9F8.54455B6E@nortelnetworks.com> <20020606.202108.52904668.davem@redhat.com> <3D01307C.4090503@candelatech.com>
On Fri, Jun 07, 2002 at 03:15:24PM -0700, Ben Greear wrote:
> David S. Miller wrote:
> > Your idea is totally useless for non-datagram sockets.
> > Only datagram sockets use the interfaces where you bump
> > the counters.
> > I don't like the patch, nor the idea behind it, at all.
> Datagram sockets are the ones that drop data though (tcp will
> deal with it via re-transmits).
Outside of the specific changes suggested by Chris, I can see a
requirement to be able to detect poor connections. While TCP/IP may
not drop packets from the perspective of user space applications,
TCP/IP packets do get lost. For certain applications that require high
bandwidth, or low latency, applications may be able to optimize code
paths by analyzing statistics related to the socket.
Datagram sockets are more straight forward to implement this for, but
that does not mean that TCP/IP does not have similar potential.
I am not certain what the exact requirement is for in Chris' cases,
but I do know that in his field, he is writing something far more
complicated and resource intensive than a telnet server.
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2002-06-08 21:11 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 19:37 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 [this message]
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
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=20020608170511.B26821@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=cfriesen@nortelnetworks.com \
--cc=davem@redhat.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®