From: Michael Ulitskiy <mdu113@acedsl.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Prio queue with many bands
Date: Fri, 06 Jun 2003 19:26:31 +0000 [thread overview]
Message-ID: <marc-lartc-105492878332055@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105491819419394@msgid-missing>
On Friday 06 June 2003 02:40 pm, you wrote:
> On Friday 06 June 2003 18:30, Michael Ulitskiy wrote:
> > Hi,
> >
> > I'm wondering if there's any simple classfull queue like prio that supports
> > at least 256 bands? I don't care about priomap or some additional
> > functionality, I just want to divide traffic in 256 bands using hashing
> > filters using as least resources as possible. I understand I can do that
> > with htb for example, but I guess htb is much more resourse-consuming.
> Why do you think so? I think you will surprised how many active classes an
> old 486 can handle. It also depends on the maximum bandwidth the box has to
> shape.
I think so because unlike simple prio queue htb has to maintain some timers and
counters and buffers. I'm not saying that htb is heavy, but I'm quite sure that prio is lighter.
I have to shape /19 at the moment and possibly more in the future. In this case
I want to save as much resourses as possible and attach htb classes to the
simple queue bands.
Has anyone tried just to change TC_PRIO_MAX and TC_PRIO_BANDS values in
/usr/src/linux/include/linux/pkt_sched.h?
> Stef
Michael
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-06-06 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 16:30 [LARTC] Prio queue with many bands Michael Ulitskiy
2003-06-06 18:40 ` Stef Coene
2003-06-06 19:26 ` Michael Ulitskiy [this message]
2003-06-06 19:59 ` Stef Coene
2003-06-06 20:01 ` Michael Ulitskiy
2003-06-06 22:10 ` 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=marc-lartc-105492878332055@msgid-missing \
--to=mdu113@acedsl.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.