From: Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Net device byte statistics
Date: Fri, 25 Jul 2003 05:26:15 +0200 [thread overview]
Message-ID: <E19ftDj-00016j-00@calista.inka.de> (raw)
In-Reply-To: <200307250437.50928.fredrik@dolda2000.cjb.net>
In article <200307250437.50928.fredrik@dolda2000.cjb.net> you wrote:
> I almost thought that would be it. I do understand that that code needs to be
> really clean, but, correct me if I'm wrong, but isn't GCC's long long
> implementation efficient enough to only add minimal overhead to that?
I think there is mainly an issue with atomic incremets. I am not sure if the
counter can be incremeted concurrently, or if the code path would be
serialized, but there is always the reading side, which may need to retry an
read. Besides that, the counter is in the fast path, so it will add some
delay to packet handling.
I guess a 64bit implementation will need to be a per-cpu solution.
Greetings
Bernd
--
eckes privat - http://www.eckes.org/
Project Freefire - http://www.freefire.org/
next prev parent reply other threads:[~2003-07-25 3:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 23:56 Net device byte statistics Fredrik Tolf
2003-07-25 0:22 ` Bernd Eckenfels
2003-07-25 2:37 ` Fredrik Tolf
2003-07-25 3:26 ` Bernd Eckenfels [this message]
2003-07-25 3:49 ` Jeff Sipek
2003-07-25 3:54 ` Jeff Sipek
2003-07-25 7:03 ` Denis Vlasenko
2003-07-25 7:01 ` Andre Hedrick
2003-07-25 16:23 ` Jeff Sipek
2003-07-25 17:20 ` Randy.Dunlap
2003-07-25 17:55 ` Jeff Sipek
2003-07-25 17:58 ` Randy.Dunlap
2003-07-25 21:55 ` jw schultz
2003-07-25 22:51 ` Jeff Sipek
2003-07-26 0:08 ` Ben Greear
2003-07-26 0:44 ` jw schultz
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=E19ftDj-00016j-00@calista.inka.de \
--to=ecki@calista.eckenfels.6bone.ka-ip.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;
as well as URLs for NNTP newsgroup(s).