mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: lsawyer@gci.com, Ian Stirling <root@mauve.demon.co.uk>,
	linux-kernel@vger.kernel.org
Subject: RE: IP Acounting Idea for 2.5
Date: Tue, 17 Apr 2001 07:28:17 -0500 (CDT)	[thread overview]
Message-ID: <200104171228.HAA00656@tomcat.admin.navo.hpc.mil> (raw)

Leif Sawyer <lsawyer@gci.com>:
> > From: Ian Stirling [mailto:root@mauve.demon.co.uk]
> > > Manfred Bartz responded to
> > > > Russell King <rmk@arm.linux.org.uk> who writes:
> > <snip>
> > > > You just illustrated my point.  While there is a reset capability
> > > > people will use it and accounting/logging programs will get wrong
> > > > data.  Resetable counters might be a minor convenience 
> > when debugging
> > > > but the price is unreliable programs and the loss of the 
> > ability of
> > > > several programs to use the same counters.
> > > 
> > > You of course, are commenting from the fact that your 
> > applications are
> > > stupid, written poorly, and cannot handle 'wrapped' data.  Take MRTG
> > <snip>
> > > Similarly, if my InPackets are at 102345 at one read, and 
> > 2345 the next
> > > read,
> > > and I know that my counter is 32 bits, then I know i've 
> > wrapped and can do
> > 
> > I think the point being made is that if InPackets are at 
> > 102345 at one read,
> > and 2345 the next, and you know it's a 32 bit counter, it's completely
> > unreliable to assume that you have in fact recieved 4294867295
> > packets, if the counter can be zeroed.
> > You can say nothing other than at least 2345 packets, at most 
> > 2345+n*2^32 have been got since you last checked.
> 
> Ah, yes.. I seem to have misplaced a bit of text in my reply.
> 
> The continuation of thought:
> 
> How the application derives the status of a wrapped counter or
> a zero'ed counter is dependant on the device being monitored.
> 
> Yes, you have to know what your interface is capable of (maxbytes/sec)
> so that you can do a simple calculation where:
> 
> maximum_throughput = maxbytes_sec * (time_now - time_last_read)
> 
> and if your previous good counter + the maximum throughput wraps the
> counter, you have a good chance that you've simply wrapped.
> 
> If not, then you can assume that your counters were cleared at some point,
> log the data you've got, and keep moving forward.

And that introduces errors in measurement. It also depends on how frequently
an uncontroled process is clearing the counters. You may never be able to
get a valid measurement.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

             reply	other threads:[~2001-04-17 12:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 12:28 Jesse Pollard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-17 23:06 Leif Sawyer
2001-04-17 21:48 Leif Sawyer
2001-04-17 22:58 ` Manfred Bartz
2001-04-17 23:13   ` Alan Cox
2001-04-17 23:35     ` Manfred Bartz
2001-04-18  0:02       ` Alan Cox
2001-04-20  2:51         ` Ton Hospel
2001-05-01 23:13           ` Mark van Walraven
2001-04-18  8:16     ` Kenneth Johansson
2001-04-18 14:45     ` Jonathan Lundell
2001-04-17 21:25 Jesse Pollard
2001-04-17 19:09 Leif Sawyer
2001-04-17 19:37 ` Matti Aarnio
2001-04-18 13:49   ` Michael Clark
2001-04-17 22:32 ` Manfred Bartz
2001-04-17 18:31 Jesse Pollard
2001-04-17 16:57 Leif Sawyer
2001-04-16 23:52 Leif Sawyer
2001-04-16 22:35 Leif Sawyer
2001-04-16 23:42 ` Ian Stirling
2001-04-17  1:13 ` Manfred Bartz
2001-04-17 10:34 ` Olaf Titz
2001-04-16 21:53 David Findlay
2001-04-16  0:21 ` Michael Clark
2001-04-16  0:40 ` Mike A. Harris
2001-04-16 22:46   ` David Findlay
2001-04-16  0:50     ` Mike A. Harris
2001-04-16  1:58       ` swds.mlowe
2001-04-16  1:24     ` Matti Aarnio
2001-04-16  2:07     ` Manfred Bartz
2001-04-16  9:43       ` Russell King
2001-04-16 22:24         ` Manfred Bartz
2001-04-17 10:29         ` Olaf Titz
2001-04-17  1:43       ` Harald Welte
2001-04-17  2:37         ` Manfred Bartz
2001-04-17  6:56         ` Henning P. Schmiedehausen
2001-04-20 16:17           ` Harald Welte
2001-04-20 21:00             ` Henning P. Schmiedehausen
2001-04-16 11:21     ` Andreas Ferber
2001-04-16  2:40 ` Dax Kelson
2001-04-17  1:39 ` Harald Welte

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=200104171228.HAA00656@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsawyer@gci.com \
    --cc=root@mauve.demon.co.uk \
    /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®