All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonios Chalkiopoulos <alg0@iit.demokritos.gr>
To: lartc@vger.kernel.org
Subject: [LARTC] tc monitoring
Date: Thu, 30 Sep 2004 11:31:13 +0000	[thread overview]
Message-ID: <200409301431.13267.alg0@iit.demokritos.gr> (raw)

I have managed to dynamically parse the output of commands:

tc qdisc ls dev eth0 and 
tc -s class show dev eth0

Save statistics in an rrd database and display it via a php script.
see http://143.233.4.215/graph.php and dload scripts from 
http://143.233.4.210/qos/

My next step in developing this monitoring software is to somehow manage to 
create a tree out of tc and then use it to greatly improve the monitoring 
viewability. Check http://143.233.4.210/qos/applyQoS_Xylouris_v0.20.html

One way is to parse the script that installed the qdiscs into the kernel and 
through parent and handle ids to construct that tree. There is a number of 
problem in the above solution like commented tc commands, no distinction 
between functions applyHTBWondershaper() and applyCBQWondershaper() etc.

So is there a way to use the tc command and manage to get usefull information 
about which qdisc is parent and which is a leaf?

Thanks in advance for your time,

Antonios Chalkiopoulos

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-09-30 11:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 11:31 Antonios Chalkiopoulos [this message]
2004-09-30 11:59 ` [LARTC] tc monitoring 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
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=200409301431.13267.alg0@iit.demokritos.gr \
    --to=alg0@iit.demokritos.gr \
    --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.