All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] help htb class
Date: Tue, 21 May 2002 13:06:21 +0000	[thread overview]
Message-ID: <marc-lartc-102198645103089@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102198549102202@msgid-missing>

Ciprian Niculescu wrote:
> tc qdisc del dev eth0 root
> tc qdisc add dev eth0 root handle 1: htb default 5
> tc class add dev eth0 parent 1: classid 1:1 htb rate 5mbit prio 1
> 
> tc class add dev eth0 parent 1:1 classid 1:2 htb rate 3mbit prio 2
> 
> tc class add dev eth0 parent 1:2 classid 20:1 htb rate 2mbit
> RTNETLINK answers: Invalid argument

I guess it should probably either qdisc add or classid 1:3 ...

> 
> 
> i don't understand, why???
> 

from include/linux/pkt_sched.h:
/* "Handles"
    ---------

     All the traffic control objects have 32bit identifiers, or "handles".

     They can be considered as opaque numbers from user API viewpoint,
     but actually they always consist of two fields: major and
     minor numbers, which are interpreted by kernel specially,
     that may be used by applications, though not recommended.

     F.e. qdisc handles always have minor number equal to zero,
     classes (or flows) have major equal to parent qdisc major, and
     minor uniquely identifying class inside qdisc.

     Macros to manipulate handles:
  */
...

Bye,
Patrick

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-05-21 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 12:49 [LARTC] help htb class Ciprian Niculescu
2002-05-21 13:06 ` Patrick McHardy [this message]
2002-05-21 13:07 ` Alexey Talikov

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-102198645103089@msgid-missing \
    --to=kaber@trash.net \
    --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.