From: David Ananian-Cooper <davidac17@yahoo.com>
To: linux-ppp@vger.kernel.org
Subject: Re: counters overflow
Date: Wed, 29 Sep 2004 06:16:32 +0000 [thread overview]
Message-ID: <200409291604.50034.davidac17@yahoo.com> (raw)
In-Reply-To: <262655318.20040929092029@rsl.ru>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
hi
i've encountered the same problem working the code while writing a plugin. i
managed to get around it by taking a copy of the counters every few minutes
and noting when they loop around to zero (i.e. when old_value > new_value).
its a bit of a hack, but it seems to work for my purposes.
david ananian-cooper
On Wed, 29 Sep 2004 15:20, Dmitry Vereschaka wrote:
> Hello linux-ppp,
>
> The problem is that counters for 'bytes in' and 'bytes out' are 32 bit
> integers, which is enough for counting data while connected via modem, but
> really small while using pppoe or pptpd-based solutions deployed over
> 100/1000mbit network.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-29 6:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 5:20 counters overflow Dmitry Vereschaka
2004-09-29 6:16 ` David Ananian-Cooper [this message]
2004-09-29 16:10 ` Bill Unruh
2004-09-30 2:10 ` Paul Mackerras
2004-09-30 17:33 ` carlsonj
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=200409291604.50034.davidac17@yahoo.com \
--to=davidac17@yahoo.com \
--cc=linux-ppp@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;
as well as URLs for NNTP newsgroup(s).