From: Lawrence MacIntyre <lpz@ornl.gov>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Accessing TC objects via netlink interface
Date: Thu, 11 Dec 2003 13:48:15 +0000 [thread overview]
Message-ID: <marc-lartc-107115132328748@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107114958526692@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
raj:
This is one of the most sparsely documented parts of linux. The only
places I know of are:
man 3 netlink
man 7 netlink
man 3 rtnetlink
man 7 rtnetlink
the kernel source
in man netlink, you find a reference to
ftp://ftp.inr.ac.ru/ipâ€routing/iproute2* for libnetlink
The code is clearly designed to be as efficient as possible, and much of
the protocol involves context, which makes it quite difficult to figure
out. OTOH, you can do things with linux/netlink which would require
kernel mods with any other operating system, so I'm just glad it's
there.
On Thu, 2003-12-11 at 07:23, rajkumars@asianetindia.com wrote:
> Hi,
>
> While going through the README of Michal's SNMP extension, he collects stats using netlink interface. Is their any howto or other docs to learn how it works?
>
> raj
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
--
Lawrence MacIntyre 865.574.8696 lpz@ornl.gov
Oak Ridge National Laboratory
High Performance Information Infrastructure Technology Group
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-11 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 12:23 [LARTC] Accessing TC objects via netlink interface rajkumars
2003-12-11 13:48 ` Lawrence MacIntyre [this message]
2003-12-11 14:39 ` Patrick McHardy
2003-12-11 15:14 ` Michal Charvat
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=marc-lartc-107115132328748@msgid-missing \
--to=lpz@ornl.gov \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.