All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Mueller <andreas@stapelspeicher.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc del class not working
Date: Tue, 09 May 2006 22:17:59 +0000	[thread overview]
Message-ID: <20060509221759.GA3892@lintera> (raw)
In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB25530F@xavier.staff.greatlakes.net>

Hi, this is a bug in the sch_hfsc.c module, the level count doesn't get
adjusted correctly.
The following patch works for me, but is not a beauty and may be wrong.

Andreas

Eliot, Wireless and Server Administrator,  Great Lakes Internet wrote:
...
> Also, a quick test by hand shows that it is only from having a child
> class assigned to it that it becomes un-deletable. 
...
> 
> This does not:
> 
> wireless-r1 raddb # tc class add dev wivl4 parent 5:0 classid 5:56 hfsc
> ls m1 1536.0Kbit d 2000ms m2 256.00Kbit ul m2 1024Kbit
> 
> wireless-r1 raddb # tc class add dev wivl4 parent 5:56 classid 5:57 hfsc
> sc umax 1500b dmax 30ms rate 80Kbit
> 
> wireless-r1 raddb # tc class del dev wivl4 parent 5:56 classid 5:57 hfsc
> sc umax 1500b dmax 30ms rate 80Kbit
> 
> wireless-r1 raddb # tc class del dev wivl4 parent 5:0 classid 5:56 hfsc
> ls m1 1536.0Kbit d 2000ms m2 256.00Kbit ul m2 1024Kbit
> RTNETLINK answers: Device or resource busy
...
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2006-05-09 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 18:10 [LARTC] tc del class not working Eliot, Wireless and Server Administrator,  Great Lakes Internet
2006-05-09 22:17 ` Andreas Mueller [this message]
2006-05-09 22:19 ` Andreas Mueller
2006-05-10  4:43 ` Patrick McHardy

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=20060509221759.GA3892@lintera \
    --to=andreas@stapelspeicher.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.