Re: RFC: per-socket statistics on received/dropped packets

At 09:34 PM 9/06/2002 -0700, David S. Miller wrote:

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.

would you be willing to accept a patch that enables per-socket accounting 
with a CONFIG_ option?

to my mind, i can see a number of perfectly valid scenarios.
one is for streaming-media applications which could use retransmissions as 
an indication to buffer more data and/or switch to a different bitrate.

another is for a http proxy which has multiple outgoing interfaces which 
are multihomed via different providers (and some via simplex satellite).
retransmissions woud be a nice metric to use for determining the weightings 
between using different interfaces.


cheers,

lincoln.

   From: Lincoln Dale [off-list ref]
   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?

On Mon, 10 Jun 2002, David S. Miller wrote:

   From: Lincoln Dale [off-list ref]
   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.

cheers,
jamal