From: Jeff Sipek <jeffpc@optonline.net>
To: Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>,
linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@digeo.com>,
Dave Jones <davej@codemonkey.org.uk>,
Linus Torvalds <torvalds@osdl.org>,
netdev@oss.sgi.com, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH - RFC] [1/5] 64-bit network statistics - generic net
Date: Sat, 05 Jul 2003 16:37:43 -0400 [thread overview]
Message-ID: <200307051637.52252.jeffpc@optonline.net> (raw)
In-Reply-To: <E19YtAq-0006Xf-00@calista.inka.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 05 July 2003 15:58, Bernd Eckenfels wrote:
> a reader like ifconfig can easyly work around this with multiple tries, but
> incremeting those variables wont work that easy, and therefore needs a
> lock, which will be a major pita.
>
> 64bit counters should be a result of lockless per-cpu network counters
> (32bit) with some kind of async merging.
This is going to make the structure huge - not only you have the 32-bit
variables for every CPU, but you have one global set of 64-bit variables
(possibly you will need a lock for the 64-bit vars.)
Also another thing to consider is portability across architectures - we don't
need all this code on 64-bit arches.
On the other hand, per-cpu stats may possibly make up for the extra code - no
cache bouncing, etc.
> Or we wait till 64bit hardware is more common :)
Hehe, the thing is, that when 64bits beecome more common you will have this
huge number of unused x86 computers that people will:
- - throw out
- - donate
- - convert to all sorts of "embedded" systems which need stable OS (read:
Linux) (these include routers)
So, x86 is here to stay for some time.
Jeff.
- --
The Moon is Waxing Crescent (36% of Full)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/BzcbwFP0+seVj/4RAuMHAJ9sN0E4OgsPeM09D6hbgM3boECLDwCbBDTP
6u8SSobW0+Y0oWq3H4koHd0=
=Z89A
-----END PGP SIGNATURE-----
next parent reply other threads:[~2003-07-05 20:37 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 ` Jeff Sipek [this message]
2003-07-05 20:40 ` [PATCH - RFC] [1/5] 64-bit network statistics - generic net 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
[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=200307051637.52252.jeffpc@optonline.net \
--to=jeffpc@optonline.net \
--cc=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=ecki@calista.eckenfels.6bone.ka-ip.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).