public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH - RFC] [1/5] 64-bit network statistics - generic net
Date: Fri, 4 Jul 2003 11:47:45 +0200	[thread overview]
Message-ID: <20030704094745.GG29233@lug-owl.de> (raw)
In-Reply-To: <200307032231.39842.jeffpc@optonline.net>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

On Thu, 2003-07-03 22:31:27 -0400, Jeff Sipek <jeffpc@optonline.net>
wrote in message <200307032231.39842.jeffpc@optonline.net>:
Content-Description: clearsigned data
> The variables for network statistics (in struct net_device_stats) are unsigned 
> longs. On 32-bit architectures, this makes them overflow every 4GB or 2^32 
> packets. The following series of patches [against 2.5.74] makes the 
> statistics variable type configurable. The default is to leave everything the 
> way it was (unsigned long). However, when NETSTATS64 is set in the config, 
> the statistics use 64-bit variables (u_int64_t) - this works only on 32-bit 
> architectures.

Well... I don't really like to break userspace, but why don't we simply
make packet/traffic counters long long / u_int64_t? This way, we'd
simply keep almost all drivers untouched and only need to fiddle with
some sprints()/printk() statements?

Really, how many programs use the current statistics? I'd prefer to
modify them over adding strange patches like this one to the kernel...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-07-04  9:34 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
2003-07-05 21:46     ` Ben Greear
2003-07-04  9:47 ` Jan-Benedict Glaw [this message]
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=20030704094745.GG29233@lug-owl.de \
    --to=jbglaw@lug-owl.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