From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: "clean" qdisc reinit (was Re: [LARTC] HTB flooding my kernel logs)
Date: Fri, 24 Jan 2003 17:38:30 +0000 [thread overview]
Message-ID: <marc-lartc-104343013220468@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104334971821013@msgid-missing>
On Thursday 23 January 2003 20:22, Mihai RUSU wrote:
> On Thu, 23 Jan 2003, Stef Coene wrote:
> > If it works, fine for you. It's just not something I would advice :)
> > But why not delete the root qdisc and recreate it?
> >
> > Stef
>
> All started when we observed that in the meantime (the time between tc
> qdisc del and the time it takes to recreate the whole new tree) people's
> TCP connections speed increases very much, so its not very nice. We
> recreate the trees like 100 times a day so that can be a problem.
>
> So then we made the 2 trees system. While building the new tree the old
> one still "serves" packets and then we change by a simple tc filter
> change. As we observed there is still a small bandwidth increase (the
> classes are empty) but its very small compared to the other one.
>
> If you have another solution please say.
No, I havent'.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-01-24 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 19:22 "clean" qdisc reinit (was Re: [LARTC] HTB flooding my kernel logs) Mihai RUSU
2003-01-24 17:38 ` 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=marc-lartc-104343013220468@msgid-missing \
--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 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.