lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071218145707.GV11220@postel.suug.ch>
Date:	Tue, 18 Dec 2007 15:57:07 +0100
From:	Thomas Graf <tgraf@...g.ch>
To:	Mark Seger <Mark.Seger@...com>
Cc:	netdev@...r.kernel.org
Subject: Re: update frequency for stats in /proc/net/dev

* Mark Seger <Mark.Seger@...com> 2007-12-18 08:37
> Anyhow, I just wanted to let people know that ALL tools that monitor 
> once a second on older counters will get the wrong numbers and tools 
> that correct for the wrong number by using fractional intervals (and I 
> suspect mine is the only one that does) but run on newer kernels will 
> also get the wrong numbers.  In any event, if anyone is interested in 
> trying out collectl - it monitors a  LOT more than just networks - you 
> can snag a copy of from http://collectl.sourceforge.net/ if you'd like 
> to take if for a drive.  The website has a lot of output examples to 
> give you a better idea what it can do.  I even included a writeup about 
> the odd network performance observations at 
> http://collectl.sourceforge.net/NetworkStats.html

I've solved this problem by using netlink to read the interface counters
ten times per second and maintain an own counter from which I calculate
the rate exactly once per second/minute/hour. The rate per second may
still be inaccurate to some degree, therefore I keep a history of 2-5
rates and take them into account to smoothen the result. This works
fairly well with _all_ operating systems.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ