netdev
[Top] [All Lists]

Re: netdev.stats change suggestion

To: devik@xxxxxx (Martin Devera)
Subject: Re: netdev.stats change suggestion
From: kuznet@xxxxxxxxxxxxx
Date: Fri, 25 Jan 2002 21:19:14 +0300 (MSK)
Cc: davem@xxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.10.10201242214140.15162-100000@xxxxxxxxxxxx> from "Martin Devera" at Jan 24, 2 10:30:40 pm
Sender: owner-netdev@xxxxxxxxxxx
Hello!

> I can't found ifstat, nstat in my iproute 010824 .. Maybe old one ?

Yes, if appeared in the nest snapshot together with tcpdiag.

> By the way I don't see how you get over wraparound problem.

It needs sampling each sevral seconds to calculate rates,
so that the problem just does not exist. 


> in read stat part ? Fast, simple (and possibly wrong) :)

Yes. And this is exactly which I do not want to pay in addition
to storing in the kernel information which it never wants to remember.

Well, this attitude has grown as a kind of physiological reaction to
proposals sort of adding to struct net_device a Cisco-like
"interface desription" string.

The reaction is: please, start from showing something really
useful, f.e. rates. After you do this, all the problems will disappear,
you have lots of space in /etc to store description strings.
Counter wrapping is pseudoproblem of the same nature.

What will change if netstat will show numbers sort of 761586014605217?

The next step is: "Oh, well, I want to clear them!"

And this will not pass. Clearing kernel counters is hard bug,
which makes impossible interaction to multiple information consumers.

Alexey

<Prev in Thread] Current Thread [Next in Thread>