From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Pfifo_fast "Unknown qdisc" and asking for basic design
Date: Mon, 14 Nov 2005 22:36:08 +0000 [thread overview]
Message-ID: <43791158.9060501@dsl.pipex.com> (raw)
In-Reply-To: <BF782D07436CAE4B931BFA5B2C68FF4F0F8B9E@bmts1.ad.bmtseatech.co.uk>
Mark Lidstone wrote:
> Hi Andy,
>
> Many thanks for the reply.
>
> Is there a reason why the user is not supposed to use pfifo_fast? I
> don't think I need a full-on PRIO (surely pfifo_fast is more efficient
> if it is classless?). Sorry for asking, but I didn't come across this
> limitation in the documentation.
Not sure really.
>
> Following your suggestions, I've come up with the following:
>
> #!/bin/sh
> SQ="tc qdisc add dev eth0"
> SC="tc class add dev eth0"
> SF="tc filter add dev eth0"
>
> tc qdisc del dev eth0 root
> $SQ root handle 1:0 htb
> $SC parent 1:0 classid 1:1 htb rate 4096kbit
> $SC parent 1:1 classid 1:2 htb prio 0 rate 768kbit #Video
> Conferencing
> $SC parent 1:1 classid 1:3 htb prio 1 rate 1545kbit #Company 1
> $SC parent 1:1 classid 1:4 htb prio 1 rate 832kbit #Company 2
> $SC parent 1:1 classid 1:5 htb prio 1 rate 713kbit #Company 3
> $SC parent 1:1 classid 1:6 htb prio 1 rate 238kbit #Company 4
> $SQ parent 1:2 handle 5:0 prio #Video Conferencing
> $SQ parent 1:3 handle 6:0 prio #Company 1
> $SQ parent 1:4 handle 7:0 prio #Company 2
> $SQ parent 1:5 handle 8:0 prio #Company 3
> $SQ parent 1:6 handle 9:0 prio #Company 4
>
> $SF parent 1:0 protocol ip prio 0 u32 match ip src 1.2.3.4/32
> flowid 5:0
> $SF parent 1:0 protocol ip prio 0 u32 match ip src 1.2.3.5/32
> flowid 6:0
> $SF parent 1:0 protocol ip prio 0 u32 match ip src 1.2.3.6/32
> flowid 7:0
> $SF parent 1:0 protocol ip prio 0 u32 match ip src 1.2.3.7/32
> flowid 8:0
> $SF parent 1:0 protocol ip prio 0 u32 match ip src 1.2.3.8/32
> flowid 9:0
>
> (I've a horrible feeling there's something obviously and fundamentally
> wrong with this)
>
> What happens with any traffic not from these IPs?
You can use a catch all filter after the others ... u32 match u32 0 0 ..
Unlike htb prio 1 is the top prio for filters.
Without knowing what your setup is it's hard to say what's the best way
in detail eg. where and what bandwidth are the bottleneck links and
which end of them you are shaping.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-11-14 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 9:50 [LARTC] Pfifo_fast "Unknown qdisc" and asking for basic design Mark Lidstone
2005-11-11 14:22 ` Andy Furniss
2005-11-11 16:29 ` Mark Lidstone
2005-11-14 22:36 ` Andy Furniss [this message]
2005-11-15 10:31 ` Mark Lidstone
2005-11-15 18:59 ` Stephen Hemminger
2005-11-16 13:12 ` Mark Lidstone
2005-11-16 14:55 ` Andy Furniss
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=43791158.9060501@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.