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] tc classes limit
Date: Sun, 01 Feb 2004 09:27:57 +0000	[thread overview]
Message-ID: <200402011027.57651.stef.coene@docum.org> (raw)
In-Reply-To: <opr2l096yz4ddcy3@mail.elfarto.com.ar>

On Friday 30 January 2004 23:40, Gerardo Arceri wrote:
> This may be answered somewhere but i tried googling for it with no luck,
> so...
>
> What's the limit on number of traffic classes (classid) you can define on
> Linux ?
From http://docum.org/stef.coene/qos/docs/general.html :

----
Each class and qdisc has a unique number: "<major number:minor number>". For a 
qdisc the minor number is zero, or you give no number. The major number of a 
class is the same as the major number of the qdisc the class belongs to. So, 
pairs x:y are class handles and x:0 or x: are qdisc handles. 

Each major number can be a number between 1 and 0x7fff. Major number 0x8000 - 
0xffff is used for qdiscs with an unspecified major number. Numbers from 
ffff:fff0 to ffff:ffff are reserved or have a special meaning. 

The major numbers are unique for each qdisc. The minor numbers are unique per 
major number. You can use hexadecimal numbers. 

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.
 */
-----

stef

-- 
stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net

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

      parent reply	other threads:[~2004-02-01  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30 22:40 [LARTC] tc classes limit Gerardo Arceri
2004-01-31 13:30 ` Jose Luis Domingo Lopez
2004-02-01  9:27 ` 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=200402011027.57651.stef.coene@docum.org \
    --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.