From: Jeff <jeffpc@optonline.net>
To: linux-kernel@vger.kernel.org
Subject: 64-bit fields in struct net_device_stats
Date: Sun, 15 Jun 2003 21:30:47 -0400 [thread overview]
Message-ID: <200306152131.09983.jeffpc@optonline.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all,
I was looking for a project that would take some time to finish, and I think
I found it - converting all code in the kernel to use u_int64_t (or similar)
instead of unsigned long in struct net_device_stats.
Now, I have an idea on my mind about how to do this:
I'd move the structure to a new file in linux/include/asm
(linux/include/asm-{arch}/netdevice.h, for example) and implement there
couple of functions that would change the counters in the structure
(something like: static inline void net_stats_txbytes_add(struct
net_device_stats* stats, unsigned long len)). These would lock (if necessary
- - 32-bit architectures), add, unlock (if necessary.) The only thing is, that
all the NIC drivers in the kernel up to date would have to be changed to use
this new interface.
Now, my question: Is there a better way of accomplishing this?
Thanks,
Jeff.
- --
A CRAY is the only computer that runs an endless loop in just 4 hours...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+7R3XwFP0+seVj/4RAolgAJ9QE4eLfKqrVhR9tktoZCHjcfarfgCcDb1A
HELhBfYleUbTSaTymmTsRJM=
=xu4t
-----END PGP SIGNATURE-----
next reply other threads:[~2003-06-16 1:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 1:30 Jeff [this message]
2003-06-16 2:53 ` 64-bit fields in struct net_device_stats Jeff
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=200306152131.09983.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