From: Marek Kierdelewicz <marek@piasta.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Handle limit in filter
Date: Sun, 20 Aug 2006 09:23:16 +0000 [thread overview]
Message-ID: <20060820112316.2fa86329@localhost.localdomain> (raw)
In-Reply-To: <17637.48829.494838.331967@mail.linux-delhi.org>
> Kajetan> I'm generating huge tc setup from database and loading it
> Kajetan> (which takes significant amount of time) only on router
> Kajetan> startup or reloading whole router configuration.
>
> As I suspected... I wonder if Marek's solution would work in a
> significantly dynamic environment? Any thoughts Marek?
Just try it... Generating large file with tc classes and filters and
then loading it with "tc -b" takes less then 1s on most system.
If you're worried about active connections - don't be. Shaping restart
won't break them.
I use this solution on routers with thousands of filters and classess
and full restart intervals as low 1 min. It works well.
>
> Kajetan> To change speed limit of single host in network I'm using
> Kajetan> `tc class change`, which goes fast.
>
> I have to keep adding and deleting classes as users login and logout.
> I'm afraid change is not an option for me.
Whatever you do, change/add/delete you can always pack commands in one
file and load them with "tc -b". Again, it's faster.
>
> Regards,
>
> -- Raju
Regards,
--
Marek Kierdelewicz
Kierownik Dzia?u Systemów Sieciowych, KoBa
Manager of Network Systems Department, KoBa
tel. (85) 7406466; fax. (85) 7406467
e-mail: admin@koba.pl
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-08-20 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 13:33 [LARTC] Handle limit in filter Raj Mathur
2006-08-18 15:05 ` Marek Kierdelewicz
2006-08-18 19:28 ` Raj Mathur
2006-08-19 8:33 ` Kajetan Staszkiewicz
2006-08-19 9:31 ` Raj Mathur
2006-08-20 9:23 ` Marek Kierdelewicz [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=20060820112316.2fa86329@localhost.localdomain \
--to=marek@piasta.pl \
--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