From: Jeff <jeffpc@optonline.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 64-bit fields in struct net_device_stats
Date: Sun, 15 Jun 2003 22:53:29 -0400 [thread overview]
Message-ID: <200306152253.36768.jeffpc@optonline.net> (raw)
In-Reply-To: <200306152131.09983.jeffpc@optonline.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 15 June 2003 21:30, Jeff wrote:
<snip>
> These would lock (if
> necessary - 32-bit architectures), add, unlock (if necessary.)
<snip>
I now realize, that locking is out of the question. Also, it has been
suggested to use per cpu stats and overflow into a global counter. (Thanks
Zwane) This might be a better idea - the problem is, the counter won't be
100% accurate at all times. The degree of inaccuracy will vary with the
threshold value. On the other hand, if the threshold is relatively low, no
one will notice the difference these days.
Jeff.
- --
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+7TEswFP0+seVj/4RAidcAJ0UAgHtRK4F1HHp8vOSLVOc5tdtRgCfXTyN
MA5sBYybdjJxwxAwtiUnE8I=
=MbW+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-16 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 1:30 64-bit fields in struct net_device_stats Jeff
2003-06-16 2:53 ` Jeff [this message]
2003-06-16 3:12 ` Zwane Mwaikambo
2003-06-16 5:16 ` Zwane Mwaikambo
[not found] ` <Pine.LNX.4.50.0306152309220.32020-100000@montezuma.mastece nde.com>
2003-06-16 5:47 ` Lincoln Dale
2003-06-16 14:02 ` Jeff
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=200306152253.36768.jeffpc@optonline.net \
--to=jeffpc@optonline.net \
--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