From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: htb filter
Date: Mon, 28 Jun 2004 18:01:31 +0000 [thread overview]
Message-ID: <200406282001.31896.stef.coene@docum.org> (raw)
In-Reply-To: <courier.40DA5A8D.000008AD@pro-technica.com>
On Thursday 24 June 2004 06:37, lartc@pro-technica.com wrote:
> Jason Boxman writes:
> > On Wednesday 23 June 2004 01:57, Svetozar Mihailov wrote:
> >> > Shouldn't this:
> >> > > tc class add dev eth0 parent 2:0 classid 2:200 htb rate 100Mbit prio
> >> > > 10
> >> >
> >> > be "parent 2:"?
> >> >
> >> > Ed W
> >>
> >> That change nothing. I have running system with 800 PC , 4 classes for
> >> each. There is no difference for me in using "parent 2:" vs "parent
> >> 2:0". Both give same result.
> >
> > Exactly. 2: is simply a short hand for 2:0, for example.
>
> And is someone have idea how to list current configuration? I want to wrote
> similar to 'iptables-save' but for tc. In my running config there are about
> 3200 classes and 4000 filters. The script I generate is 1.2Mbytes and need
> 45 seconds to apply. I want to speedup this process with some kind of
> tc-save and tc-restore.
I wrote some scripts to save the running configuration, but it is integrated
in other, buggy, bloated script. The major problem is recognizing the
different options and qdiscs/classes.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-06-28 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 4:37 [LARTC] Re: htb filter lartc
2004-06-28 18:01 ` Stef Coene [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=200406282001.31896.stef.coene@docum.org \
--to=stef.coene@docum.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox