From: "Rask Ingemann Lambertsen" <rask@sygehus.dk>
To: netdev@oss.sgi.com
Subject: Re: A better way to get driver stats than parsing /proc/net/dev ?
Date: Wed, 21 May 2003 18:39:17 +0100 [thread overview]
Message-ID: <20030521173554.M92611@sygehus.dk> (raw)
In-Reply-To: <3E96FAE1.7030302@candelatech.com>
On Fri, 11 Apr 2003 10:26:57 -0700, Ben Greear wrote
> Jason Lunz wrote:
> > greearb@candelatech.com said:
> >
> >>Is there an ioctl or some other binary means of getting the info that
> >>/proc/net/dev provides?
> >
> > You can do it with netlink sockets. See print_linkinfo() in the iproute2
> > code.
>
> Seems that a lot of code is needed just to read the stats :(
Maybe it is easier to parse the output from "ip -s -s link show [iface]". At
least you get all the counters, which you don't from /proc/net/dev.
--
Regards,
Rask Ingemann Lambertsen
prev parent reply other threads:[~2003-05-21 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 7:56 A better way to get driver stats than parsing /proc/net/dev ? Ben Greear
2003-04-11 15:19 ` Jason Lunz
2003-04-11 17:26 ` Ben Greear
2003-05-21 17:39 ` Rask Ingemann Lambertsen [this message]
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=20030521173554.M92611@sygehus.dk \
--to=rask@sygehus.dk \
--cc=netdev@oss.sgi.com \
/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).