From: Alexandru Matei <alex@qb.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] multiple wrr as child of htb
Date: Mon, 23 Jan 2006 14:53:53 +0000 [thread overview]
Message-ID: <43D4EE01.403@qb.ro> (raw)
In-Reply-To: <43D0B7B2.2050700@gmail.com>
Thanks all for your answer. I'll see how it will behave in practice and
let you know.
Thanks again,
Alex
Peter Surda wrote:
> Alexandru Matei schrieb:
>
>> Ok, maybe I was not clear enough.
>
>
> Yes you were :-)
>
>> What I'm interested in is the order of passing throught filters. WRR
>> has an built-in filter.
>
>
> Yes. But this isn't anything special per se, any classful qdisc
> distributes packets somehow, you just usually "tune" it by using tc
> filter.
>
>> HTB child classes are fed by matching certain ip addresses (in my
>> case htb chlid1 is for x.x.x.0/29, htb child2 is for x.x.x.8/29 )
>> and so on.
>
>
> Yes.
>
>> I want to attach wrr1 as child to htb child 1 so the traffic get
>> even divided between clients x.x.x.0/29, wrr2 as child to htb child 2
>> and so on.
>
>
> That isn't a problem (other than potential stability issues I
> mentioned before).
>
>> What I don't know is:
>> 1/ tc filter match for is evaluated first
>
>
> Of course.
>
>> 2/ if wrr1 is going to classify only hosts seen in x.x.x.0/29 or all
>> hosts x.x.x.0/24
>
>
> WRR classifies those packets that "flow" through it, like any other
> qdisc. It doesn't care whether they are a /29 subnet or some arbitrary
> IPs (it uses hashing in a way similar to conntrack for assigning
> classes).
>
>> Regards,
>> Alex
>
>
> Yours sincerely,
> Peter
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-01-23 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 10:13 [LARTC] multiple wrr as child of htb at.matei
2006-01-20 12:39 ` Gabriel
2006-01-20 13:39 ` Peter Surda
2006-01-20 13:53 ` at.matei
2006-01-20 14:32 ` Alexandru Matei
2006-01-23 14:53 ` Alexandru Matei [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=43D4EE01.403@qb.ro \
--to=alex@qb.ro \
--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.