From: "Markus Hästbacka" <midian@ihme.org>
To: root@chaos.analogic.com
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>, netdev@oss.sgi.com
Subject: Re: [NET] 64 bit byte counter for 2.6.3
Date: Wed, 18 Feb 2004 22:43:34 +0200 [thread overview]
Message-ID: <1077137014.18843.10.camel@midux> (raw)
In-Reply-To: <Pine.LNX.4.53.0402181527000.7318@chaos>
On Wed, 2004-02-18 at 22:32, Richard B. Johnson wrote:
> Manipulation of a 'long long' is not atomic in 32 bit architectures.
> Please explain how we don't care, if we shouldn't care. Also some
> /proc entries might get read incorrectly with existing tools.
Please, tell me all the tools, I'll test them. ifconfig and netstat
works correctly atleast.
And about the caring, is rx/tx bytes so important that they can't use
long long? I would care to see more than 4GB, and maybe some error in
the counter at some point (Have you _ever_ seen that happen?) than only
4GB.
And no, I didn't post this to be merged into the mainline kernel, just
to let users know that there maybe is an option for seeing maximum 4GB.
This has been working for me since, umm.. let's say 2.4.20. All the
tools I've needed have worked.
Markus
next prev parent reply other threads:[~2004-02-18 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1077123078.9223.7.camel@midux>
2004-02-18 18:17 ` [NET] 64 bit byte counter for 2.6.3 Stephen Hemminger
[not found] ` <Pine.LNX.4.53.0402181527000.7318@chaos>
2004-02-18 20:43 ` Markus Hästbacka [this message]
2004-02-18 22:45 ` Richard B. Johnson
2004-02-18 22:57 ` Stephen Hemminger
2004-02-18 23:17 ` Jeff Garzik
2004-02-19 8:14 ` Meelis Roos
2004-02-19 17:27 ` 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=1077137014.18843.10.camel@midux \
--to=midian@ihme.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=root@chaos.analogic.com \
/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).