From: Francisco Pereira <fpereira@lojan.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc monitoring
Date: Thu, 30 Sep 2004 13:49:50 +0000 [thread overview]
Message-ID: <1096552190.415c0efe53f56@webmail.montevideo.com.uy> (raw)
In-Reply-To: <200409301431.13267.alg0@iit.demokritos.gr>
Quoting Andreas Klauer <Andreas.Klauer@metamorpher.de>:
> Am Thursday 30 September 2004 14:44 schrieb Antonios Chalkiopoulos:
> > The only limitation i noticed so far is that it can not properly parse
> > the virtual channels of GRED qdisc. GRED is a tricky qdisc as it can
> > contain 1..16 RED qdisc as virtual channels.
>
> Ah, sorry, I've never used GRED before, and I wanted to avoid
> QDisc-specific parsing as much as possible. The tc command really isn't
> suited for this kind of application. I really wish there was a library
> with a decent API that lets you access this data directly. Parsing tc
> output is just a bad hack. ;)
I know of these projects, but only lql seems to be active.
Linux QoS Library (lql)
http://www.coverfire.com/lql/
An API for Linux QoS Support
http://www.ittc.ukans.edu/~pramodh/courses/linux_qos/mainpage.html
TC API Projec
http://www-124.ibm.com/developerworks/projects/tcapi
----------------------------------------------------------
0909 2468 La conexion discada a internet del Portal
La misma conexion pero MEJOR y MAS BARATA
Bajate el discador en http://www.montevideo.com.uy/0909
_______________________________________________
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-09-30 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 11:31 [LARTC] tc monitoring Antonios Chalkiopoulos
2004-09-30 11:59 ` Andreas Klauer
2004-09-30 12:02 ` Thomas Graf
2004-09-30 12:44 ` Antonios Chalkiopoulos
2004-09-30 13:06 ` Andreas Klauer
2004-09-30 13:49 ` Francisco Pereira [this message]
2004-09-30 14:37 ` Jason Boxman
2004-09-30 15:33 ` Michael S. Kazmier
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=1096552190.415c0efe53f56@webmail.montevideo.com.uy \
--to=fpereira@lojan.com \
--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.