linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Sipek <jeffpc@optonline.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>,
	Dave Jones <davej@codemonkey.org.uk>,
	Jeff Garzik <jgarzik@pobox.com>,
	netdev@oss.sgi.com
Subject: Re: [PATCH - RFC] [1/5] 64-bit network statistics - generic net
Date: Sat, 05 Jul 2003 14:49:20 -0400	[thread overview]
Message-ID: <200307051449.32934.jeffpc@optonline.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0307032005340.8468-100000@home.osdl.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 03 July 2003 23:08, you wrote:
> Please do this in user space. The "overflow every 2^32 packets" thing is
> _not_ a problem, if you just gather the statistics at any kind of
> reasonable interval.
<snip>

While discussing this patch on IRC, an interesting idea came up: why not make 
the counters count something different from bytes? "Less granular stats are 
every bit (bad pun intended) as useful." This would break userspace, but 
that's what everyone has to expect during odd releases (i.e. the modules in 
2.5.)

To avoid having to change all the code, we could have (in addition to what we 
currently have) something like tx_kbytes or tx_mbytes which would be updated 
via a timer every x milliseconds (I'd say maybe 350-500). The sysfs and 
procfs interfaces would have to be modified, however those are just couple of 
lines of code.

Using KB would give us additional 10 bits (making the overflow at 4 TB.) I 
don't really like the idea of using MB, but the underlying idea is the same - 
20 more bits, making the limit 4 PB.

What is the consensus on this way of solving the problem?

Jeff.

- -- 
Failure is not an option,
It comes bundled with your Microsoft product.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD4DBQE/Bx23wFP0+seVj/4RApsVAJUaKZG6px09U87j6tCakrQQebj6AKC52f55
xSuyYxe62N8kefAoxposfg==
=As/F
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2003-07-05 18:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-04  2:31 [PATCH - RFC] [1/5] 64-bit network statistics - generic net Jeff Sipek
2003-07-04  2:46 ` Jeff Garzik
2003-07-04  6:02   ` Jeff Sipek
2003-07-04  3:08 ` Linus Torvalds
2003-07-04  5:27   ` Jeff Sipek
2003-07-04  7:05   ` bert hubert
2003-07-05 18:49   ` Jeff Sipek [this message]
2003-07-05 21:46     ` Ben Greear
2003-07-04  9:47 ` Jan-Benedict Glaw
2003-07-04 17:57   ` Jeff Sipek
2003-07-05 19:58     ` Bernd Eckenfels
2003-07-05 20:37       ` Jeff Sipek
2003-07-05 20:40         ` Jeff Garzik
2003-07-05 20:59           ` Jeff Sipek
2003-07-05 21:51             ` Francois Romieu
2003-07-05 22:39               ` Jeff Sipek
2003-07-05 23:44                 ` Francois Romieu
2003-07-05 22:54               ` Roland Dreier
2003-07-05 21:41           ` Ben Greear
2003-07-06  7:27             ` Alan Cox

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=200307051449.32934.jeffpc@optonline.net \
    --to=jeffpc@optonline.net \
    --cc=akpm@digeo.com \
    --cc=davej@codemonkey.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=torvalds@osdl.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).