All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB flooding my kernel logs
Date: Thu, 23 Jan 2003 18:50:45 +0000	[thread overview]
Message-ID: <marc-lartc-104334960220463@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104313862704874@msgid-missing>

On Thursday 23 January 2003 00:58, Mihai RUSU wrote:
> Hi Stef
>
> On Wed, 22 Jan 2003, Stef Coene wrote:
> > So the quantum errors are gone?
>
> Yes, thanks again for the tips
>
> > > Help ? :)
> >
> > A htb qdisc attached to a htb class is useless and will only eat cpu
> > cycles.
> >
> > Stef
>
> What do you mean ? They seem to work just fine. Im no interested in any
> effect other than beeing able to delete the whole tree from a single
> command (and deleting the htb qdisc does that) so thats why I created 2
> qdiscs inside 2 htb classes. Are there any nasty side effects ? Can you
> give me some more details ? Thanks
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

-- 

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/

      parent reply	other threads:[~2003-01-23 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21  8:43 [LARTC] HTB flooding my kernel logs Mihai RUSU
2003-01-21 11:55 ` Catalin Bucur
2003-01-21 16:40 ` Stef Coene
2003-01-22  9:46 ` Mihai RUSU
2003-01-22 11:43 ` Catalin BOIE
2003-01-22 17:14 ` Stef Coene
2003-01-22 23:58 ` Mihai RUSU
2003-01-23 18:50 ` 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-104334960220463@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.