From: Thomas Graf <tgraf@suug.ch>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Qdisc statistics project
Date: Thu, 14 Oct 2004 18:55:59 +0000 [thread overview]
Message-ID: <20041014185559.GS21977@postel.suug.ch> (raw)
In-Reply-To: <200410121632.38611.alg0@iit.demokritos.gr>
> The development of these scripts is stopped. I'm rebuilding my house, making
> a website, I'm a father for 6 months now, ...... but if an interesting
> project is started, I want to help.
In order to not run into duplicated projects:
libnl
General purpose netlink library for all netlink users with different
API levels from raw netlink messaging to abstract processing of
already existing netlink users. It supports a generic caching
interface with filtering on all levels. All modules may be compiled
in or loaded at runtime.
Status
netlink messaging needs some work to handle special cases
link finished and tested
neighbour finished and tested
qdisc/class nearly finished
cbq nearly finished
fifo finished and tested
prio finished and tested
sfq finished and tested
...
filters nearly finished
u32 finished and tested
...
address TLV parsers done
route TLV parsers done
The reason for not working on LQL are licensing issues not acceptable
to me. I will release this library in 2-3 weeks and accept patches
from that point.
bmon
bmon is a portable bandwidth monitor running on various operating
systems. It supports various input methods, one of those being the
above libnl resulting in support for tc statistics. Variout output
modes exist including an interactive curses interface:
http://people.suug.ch/~tgr/bmon_ingress.jpg
but also lightweight HTML output:
http://people.suug.ch/~tgr/stats/axs.4.s.html
Statistics may be distributed over a network using multicast
or unicast and collected at some point to generate a summary
of statistics for a set of nodes.
I'm about to release 1.0-pre1 once I fixed the multicast issues
on SunOS.
netconfig
Cisco IOS like iproute2 replacement fully based on netlink
supporting full tab completion and command description for those
familiar with IOS. It is far from being releaseable as libnl
needs to be finished first. Ideas exist to use it as interface
for the new ietf netconf protocol.
generic netlink network statistics
A few of may have noticed the first small set of patches going
into 269rc3 introducing generic network statistics which will
make the process of adding new statistics to qdiscs/class/filters
very easy and removes the issue of backward compatibility.
netlink errors
Effort has gone into improving error codes/messages returned
from netlink users in the kernel. The idea is currently on hold
as all acceptable solutions would break APIs. Planned for 2.7
as of now.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-10-14 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 13:32 [LARTC] Qdisc statistics project Antonios Chalkiopoulos
2004-10-13 21:55 ` Jose Luis Araujo
2004-10-13 22:12 ` Jason Boxman
2004-10-14 5:18 ` Dan Siemon
2004-10-14 8:39 ` Antonios Chalkiopoulos
2004-10-14 18:22 ` Stef Coene
2004-10-14 18:55 ` Thomas Graf [this message]
2004-10-14 20:17 ` Stephen Hemminger
2004-10-14 20:27 ` Thomas Graf
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=20041014185559.GS21977@postel.suug.ch \
--to=tgraf@suug.ch \
--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.