From: Chris Friesen <cfriesen@nortelnetworks.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: RFC: per-socket statistics on received/dropped packets
Date: Fri, 07 Jun 2002 11:34:35 -0400 [thread overview]
Message-ID: <adqk59$d9$2@main.gmane.org> (raw)
In-Reply-To: 20020606.202108.52904668.davem@redhat.com
"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.
Thanks for the feedback.
I buy the point about it only making sense for datagram sockets in its current
form. Thus it would maybe make more sense to use udp_ioctl() rather than in the
generic socket ioctl.
However, what do you have against the basic idea of a program knowing how many
packets have
been dropped on its sockets? I added the feature to try and figure out where
packets were being dropped in an app I am developing, and so far its been very
useful.
More generally, is there a generic place that I could tie into for the counter
increment that would work for all sockets? While tcp would automatically handle
the dropped packets, it might be useful to know how many there were.
Thanks,
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2002-06-07 15:34 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 [this message]
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
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] <Pine.LNX.4.44.0206120930160.29780-100000@netcore.fi>
2002-06-12 6:49 ` 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] <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='adqk59$d9$2@main.gmane.org' \
--to=cfriesen@nortelnetworks.com \
--cc=davem@redhat.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;
as well as URLs for NNTP newsgroup(s).