From: Ben Greear <greearb@candelatech.com>
To: Jan-Philip gehrcke <jgehrcke@googlemail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Read sent/received bytes -- without opening a file in /sys or /proc
Date: Thu, 17 Feb 2011 09:32:55 -0800 [thread overview]
Message-ID: <4D5D5BC7.50802@candelatech.com> (raw)
In-Reply-To: <4D5CFF19.6050400@googlemail.com>
On 02/17/2011 02:57 AM, Jan-Philip gehrcke wrote:
> Dear list,
>
> I'm about to write a small C program for measurements of the bandwidth
> on some network interface of my home router (uname -a: Linux
> fritz.fonwlan.box 2.6.19.2 #2 Thu Nov 18 16:35:17 CET 2010 mips
> GNU/Linux). I would like to accomplish very *precise* results, while
> keeping the absolute measurement time low.
>
> In general, this problem requires the knowledge of time and byte
> differences. Therefore, two time measurements and two byte counter
> measurements for each, received and sent bytes, are required. Currently,
> I am measuring time via
>
> clock_gettime(CLOCK_MONOTONIC, ...)
>
> and reading the byte counters by reading files in sysfs, e.g.
>
> /sys/class/net/${interface}/statistics/rx_bytes.
>
> This is very easy and works well, but reading these files four times
> takes some (varying) time* on my device, which introduces an error to my
> calculation.
>
> Hence, I am wondering, if there is a way to receive this kind of data
> directly and much faster, via "kernel API". My question is related to
> this unanswered one from 2005:
> http://linux.derkeiler.com/Mailing-Lists/RedHat/2005-02/0557.html
>
> *On my device, reading such a file and interpreting the result as
> integer takes 1-10 ms, measured via:
>
> clock_gettime(CLOCK_MONOTONIC,&t_start);
> rx_bytes = read_int_from_file("/sys/class/net/wan/statistics/rx_bytes");
> clock_gettime(CLOCK_MONOTONIC,&t_end);
>
> read_int_from_file() basically consists of fopen(), fgets(), and sscanf().
>
>
> Please note that I don't have kernel/driver programming experience so far.
>
> Thank you for help and any suggestions!
>
> Jan-Philip Gehrcke
The netlink API can get stats for you, but I don't know if it would
be any more accurate time-wise. It's not exactly trivial to
implement this API, but you can look at the 'ip' program to get
an idea:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git
There is also /proc/net/dev, but that may be worse than using sysfs
as far as performance and time accuracy goes.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-02-17 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 10:57 Read sent/received bytes -- without opening a file in /sys or /proc Jan-Philip gehrcke
2011-02-17 17:32 ` Ben Greear [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-17 10:47 Jan-Philip Gehrcke
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=4D5D5BC7.50802@candelatech.com \
--to=greearb@candelatech.com \
--cc=jgehrcke@googlemail.com \
--cc=netdev@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).