From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.DE>
To: linux-kernel@vger.kernel.org
Subject: Re: overflows in /proc/net/dev
Date: Thu, 18 Aug 2005 19:30:46 +0200 [thread overview]
Message-ID: <de2gk6$nb6$1@sea.gmane.org> (raw)
In-Reply-To: 20050818163358.GA19554@taniwha.stupidest.org
Chris Wedgwood <cw@f00f.org> wrote:
> On Thu, Aug 18, 2005 at 09:28:10AM +0200, Sebastian Cla?en wrote:
>> in struct net_device_stats all members are defined as unsgined
>> long. In time of gigabit ethernet this takes not long to overflow.
> It should still take an appreciable amount of time surely? We can
With 100MBit it took about 5 minutes to overflow the 32bit byte counters
(too less for typical mrtg and Nyquist-Shannon sampling theorem in
mind), with 1GBit it takes about 30 seconds.
If you consider this appreciable... well :)
> detect those wraps in userspace and deal with it as needed.
Of course, it's usually enough time for a typical userspace application
to get scheduled at least twice.
regards
Mario
--
User sind wie ideale Gase - sie verteilen sich gleichmaessig ueber alle Platten
next prev parent reply other threads:[~2005-08-18 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 7:28 overflows in /proc/net/dev Sebastian Claßen
2005-08-18 16:33 ` Chris Wedgwood
2005-08-18 17:30 ` Mario 'BitKoenig' Holbe [this message]
2005-08-18 21:32 ` David S. Miller
2005-08-18 22:13 ` Stephen Hemminger
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='de2gk6$nb6$1@sea.gmane.org' \
--to=mario.holbe@tu-ilmenau.de \
--cc=linux-kernel@vger.kernel.org \
/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