From: "Paul C. Diem" <PCDiem@FoxValley.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] PRIO type qdisc
Date: Thu, 19 Dec 2002 00:01:40 +0000 [thread overview]
Message-ID: <marc-lartc-104025618207192@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104010520627418@msgid-missing>
On Wed, 18 Dec 2002, Hayden Myers wrote:
> > > > I'm looking for a PRIO type qdisc which will prioritize packets (either
> > > > based on DS or filters). Unlike PRIO, I need all the classes to flow into
> > > > a single qdisc (HTB). For example:
> > > >
> > > > PRIO
> > > >
> > > > +--------+--------+
> > > >
> > > > Band0 Band1 Band2
> > > >
> > > > +--------+--------+
> > > >
> > > > HTB
> > > >
> > > > Does such a qdisc exist or is there a way to get all the PRIO classes to
> > > > flow into a single qdisc?
> > > There is no such qdisc. And I don't think there is such way.
> > >
> > > But why do you want to do this?
> >
> I had wanted to do similar things a while back before 10 other things beat
> me over the head and set me back. It's funny because the above topology
> is exactly what I had envisioned but read that it was impossible. My
> setup is to have a number of users who have bandwidth limiting based on an
> ip but also does priority shaping as well. I finally decided that I could
> have a top level htb qdisc for the total box bandwidth with seperate
> classes for the users below the box bandwidth qdisc. Underneath each
> user's class I thought that I could possibly attach a prio qdisc to do
> independent priority scheduling. I don't know if this works. It was just
> a thought I had. If think the manpage shows that you can attach a prio
> to any class. Does this work and is it a feasable setup?
Right now we have one htb qdisc at the root and a class under it for each
user. We could put a prio qdisc at the root and use htb under each of
prio's band classes. This gets ridiculously complex though as you get more
link levels. I'd really like to be able to priorize the packets at each
node though so that higher priority packets take precendence at each link
(not just at the main link).
Paul C. Diem
PCDiem@FoxValley.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-19 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 6:05 [LARTC] PRIO type qdisc Paul C. Diem
2002-12-18 21:45 ` Stef Coene
2002-12-18 22:48 ` Paul C. Diem
2002-12-18 23:14 ` Hayden Myers
2002-12-19 0:01 ` Paul C. Diem [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=marc-lartc-104025618207192@msgid-missing \
--to=pcdiem@foxvalley.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox