From: Mark Mielke <mark@mark.mielke.cc>
To: jamal <hadi@cyberus.ca>
Cc: "David S. Miller" <davem@redhat.com>,
ltd@cisco.com, greearb@candelatech.com,
cfriesen@nortelnetworks.com, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: RFC: per-socket statistics on received/dropped packets
Date: Mon, 10 Jun 2002 09:57:02 -0400 [thread overview]
Message-ID: <20020610095702.A27037@mark.mielke.cc> (raw)
In-Reply-To: <Pine.GSO.4.30.0206100821310.20296-100000@shell.cyberus.ca>; from hadi@cyberus.ca on Mon, Jun 10, 2002 at 08:24:44AM -0400
On Mon, Jun 10, 2002 at 08:24:44AM -0400, jamal wrote:
> On Mon, 10 Jun 2002, David S. Miller wrote:
> > From: Lincoln Dale <ltd@cisco.com>
> > Date: Mon, 10 Jun 2002 22:03:25 +1000
> > would you be willing to accept a patch that enables per-socket
> > accounting with a CONFIG_ option?
> > What is the point?
> > If all the dists will enable it then everybody eats the overhead.
> > If the dists don't enable it, how useful is it and what's so wrong
> > with it being an external patch people just apply when they need to
> > diagnose something like this?
> I think i would agree with Dave for it to be an external patch. You
> really only need this during debugging. I had a similar patch when
> debugging NAPI about a year ago. I didnt find it that useful after
> a while because i could deduce the losses from SNMP/netstat output.
In your case you found that you could solve it once by debugging the
application.
This doesn't mean that other applications would not be better at
determining the code path to use at execution time.
Just because eth1 is behaving perfectly (i.e. low overall dropped UDP
packets, or low TCP/IP retransmission) does not mean that a specific
socket currently on eth1 heading to China should assume that it can
take the 'average' observation as adequate for observing the specific
socket.
There *are* applications that would benefit from making this decision
at run time on a socket-by-socket basis. It is not a common requirement
for most desktop users, but it remains a valid requirement.
Providing it as a patch, can have the effect that it becomes more trouble
than it is worth to grant other people access to the feature, especially
from a corporate environment that has signed off on being able to release
patches made to Linux back to the Linux source tree.
Seems somewhat of a loss...
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-10 13:57 UTC|newest]
Thread overview: 53+ 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
[not found] ` <3D01307C.4090503@candelatech.com>
2002-06-08 21:05 ` Mark Mielke
2002-06-08 23:04 ` David S. Miller
[not found] ` <20020608.160407.101346167.davem@redhat.com>
2002-06-09 0:13 ` Ben Greear
[not found] ` <3D029DAF.5040006@candelatech.com>
2002-06-09 0:51 ` David S. Miller
[not found] ` <20020608.175108.84748597.davem@redhat.com>
2002-06-09 18:23 ` Ben Greear
2002-06-10 4:34 ` David S. Miller
[not found] ` <20020609.213440.04716391.davem@redhat.com>
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 [this message]
2002-06-10 14:45 ` jamal
2002-06-10 14:56 ` jamal
2002-06-10 19:28 ` Chris Friesen
2002-06-10 19:28 ` Chris Friesen
2002-06-10 19:28 ` Chris Friesen
2002-06-10 19:28 ` Chris Friesen
2002-06-10 19:28 ` Chris Friesen
2002-06-11 22:41 ` Bill Davidsen
[not found] ` <Pine.LNX.3.96.1020611183218.29598A-100000@gatekeeper.tmr.com>
2002-06-12 3:41 ` David S. Miller
2002-06-12 3:57 ` Richard Guy Briggs
2002-06-12 5:20 ` Mark Mielke
[not found] ` <20020612012004.A15773@mark.mielke.cc>
2002-06-12 6:08 ` Pekka Savola
2002-06-12 9:18 ` Sean Hunter
2002-06-09 14:47 ` Pekka Pietikäinen
[not found] <Pine.LNX.4.44.0206120905510.29780-100000@netcore.fi>
2002-06-12 6:26 ` Ben Greear
[not found] <Message from Ben Greear <greearb@candelatech.com>
[not found] ` <3D06E9A0.5060801@candelatech.com>
2002-06-12 6:32 ` Pekka Savola
2002-06-12 12:11 ` Horst von Brand
[not found] ` <200206121211.g5CCBjZt030139@pincoya.inf.utfsm.cl>
2002-06-12 12:28 ` Lincoln Dale
[not found] <Pine.LNX.4.44.0206120930160.29780-100000@netcore.fi>
2002-06-12 6:49 ` Ben Greear
[not found] <5.1.0.14.2.20020612224038.0251bd08@mira-sjcm-3.cisco.com>
2002-06-12 13:00 ` jamal
[not found] ` <Pine.GSO.4.30.0206120853320.799-100000@shell.cyberus.ca>
2002-06-12 14:53 ` Mark Mielke
2002-06-12 14:53 ` Mark Mielke
[not found] ` <5.1.0.14.2.20020614100914.01adca48@mira-sjcm-3.cisco.com>
2002-06-14 15:51 ` Stephen Hemminger
[not found] ` <1024069878.20676.1.camel@dell_ss3.pdx.osdl.net>
2002-06-14 18:09 ` Ben Greear
[not found] <20020612105355.A20760@mark.mielke.cc>
2002-06-12 15:57 ` jamal
2002-06-12 17:00 ` Horst von Brand
-- strict thread matches above, loose matches on Subject: below --
2002-06-12 20:30 Yan-Fa Li
2002-06-12 20:30 Yan-Fa Li
[not found] <5.1.0.14.2.20020612221925.0283fb18@mira-sjcm-3.cisco.com>
2002-06-12 12:33 ` jamal
2002-06-12 12:44 ` Lincoln Dale
2002-06-12 12:44 ` Lincoln Dale
2002-06-12 12:44 ` Lincoln Dale
2002-06-13 7:21 ` David Schwartz
[not found] ` <20020613072155.AAA14363@shell.webmaster.com@whenever>
2002-06-13 8:44 ` Lincoln Dale
2002-06-23 2:03 ` Alan Cox
[not found] ` <E17LwjD-0003hT-00@the-village.bc.nu>
2002-06-23 2:05 ` Lincoln Dale
[not found] <5.1.0.14.2.20020613183120.03222cb8@mira-sjcm-3.cisco.com>
2002-06-13 10:10 ` David Schwartz
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=20020610095702.A27037@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=cfriesen@nortelnetworks.com \
--cc=davem@redhat.com \
--cc=greearb@candelatech.com \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=ltd@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).