From: Werner Almesberger <wa@almesberger.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] [tcng] drawing with gnuplot
Date: Fri, 19 Jul 2002 21:58:39 +0000 [thread overview]
Message-ID: <marc-lartc-102711591906657@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102710109423848@msgid-missing>
raptor@unacs.bg wrote:
> Is there a way with tcsim to see how different channels got used i.e. say
> I have three channels
There's no general way to distinguish classes (*). However, since
you select by source IP address, you can let tcsim_filter split flows
by that:
tcsim ... | tcsim_filter ... src | tcsim_plot
(*) In principle, I could export skb->tc_index, which is always set
when using the egress or ingress qdiscs, but since skb->tc_index
gets assigned some more-or-less arbitrary values, additional
information would be needed to make this data useful. Perhaps
something to consider after switching from tcsim to umlsim.
> I read the whole tcng there is no one full example of say cbq and/or
> tbf usage (for beginners :") ). :"(
Not sure if this helps, but there is examples-ng/tbf
In general, the tcng documentation doesn't try to explain how to use
the qdiscs (semantics, parameters, etc.), since all that is basically
the same as with "tc".
> PS. I got errors on "make test", tommorow will save it on fdd and will
> post them on the list ....
"make test" errors are always interesting :-)
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://icapeople.epfl.ch/almesber/_____________________________________/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-07-19 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 17:48 [LARTC] [tcng] drawing with gnuplot raptor
2002-07-19 21:58 ` Werner Almesberger [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=marc-lartc-102711591906657@msgid-missing \
--to=wa@almesberger.net \
--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.