From: Jose Luis Domingo Lopez <lartc@24x7linux.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc classes limit
Date: Sat, 31 Jan 2004 13:30:20 +0000 [thread overview]
Message-ID: <20040131133020.GA3337@localhost> (raw)
In-Reply-To: <opr2l096yz4ddcy3@mail.elfarto.com.ar>
On Friday, 30 January 2004, at 19:40:44 -0300,
Gerardo Arceri wrote:
> What's the limit on number of traffic classes (classid) you can define on
> Linux ?
>
Digging in the source code of Linux kernel 2.6.1 it seems that internal
data structures for the classful queuing disciplines use a "u32"
(unsigned 32-bit long integer) to store the class ID. Maybe there is a
lower limit around there though.
Greetings.
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.6.2-bk3)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-01-31 13:30 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 [this message]
2004-02-01 9:27 ` Stef Coene
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=20040131133020.GA3337@localhost \
--to=lartc@24x7linux.com \
--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.