netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Jeff Sipek <jeffpc@optonline.net>,
	Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net.sgi.com>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>,
	Dave Jones <davej@codemonkey.org.uk>,
	Linus Torvalds <torvalds@osdl.org>,
	netdev@oss.sgi.com
Subject: Re: [PATCH - RFC] [1/5] 64-bit network statistics - generic net
Date: Sat, 05 Jul 2003 14:41:00 -0700	[thread overview]
Message-ID: <3F0745EC.1060204@candelatech.com> (raw)
In-Reply-To: <3F0737D1.5090109@pobox.com>

Jeff Garzik wrote:
> The net stats are already unsigned long internally.
> 
> 64-bit case is handled quite nicely today, thanks :)
> 
> I'm such a 64-bit bigot that "buy a 64-bit computer" is a solution I 
> commonly suggest, and it seems to fit well here, too.
> 
>     Jeff, wondering if Intel will bother to compete w/ Athlon64

Untill the net-stats are 64-bit on 32-bit systems, we will need some
way to know if they have wrapped or not when reading from nettool
and getting 64-bit numbers.

I guess what I really mean to say is that, if nettool is returning 64-bit
values, we need to know which ones are obtained from 32-bit counters.
32 -> 64 bit mapping will require wrap handling on low 32-bits, but
64 -> 64 bit mapping will require wrapping about 4-billion times less often :)

Perhaps a precision field is also needed for backwards/forwards compatability,
and perhaps a nettool version field as well to also help with backwards/forwards
compat.

Ben

> 
> 
> 


-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

  parent reply	other threads:[~2003-07-05 21:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E19YtAq-0006Xf-00@calista.inka.de>
2003-07-05 20:37 ` [PATCH - RFC] [1/5] 64-bit network statistics - generic net 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 [this message]
2003-07-06  7:27       ` Alan Cox
     [not found] <Pine.LNX.4.44.0307032005340.8468-100000@home.osdl.org>
2003-07-04  5:27 ` Jeff Sipek
2003-07-05 18:49 ` Jeff Sipek
2003-07-05 21:46   ` Ben Greear
     [not found] <200307032231.39842.jeffpc@optonline.net>
2003-07-04  2:46 ` Jeff Garzik
2003-07-04  6:02   ` Jeff Sipek
     [not found] ` <20030704094745.GG29233@lug-owl.de>
2003-07-04 17:57   ` Jeff Sipek

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=3F0745EC.1060204@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=akpm@digeo.com \
    --cc=davej@codemonkey.org.uk \
    --cc=ecki@calista.eckenfels.6bone.ka-ip.net.sgi.com \
    --cc=jeffpc@optonline.net \
    --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).