Differences between version 9 and previous revision of TrafficControl.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 9 | Last edited on Thursday, March 5, 2009 11:01:08 am | by PerryLorier | Revert |
| Older page: | version 8 | Last edited on Thursday, March 5, 2009 10:58:57 am | by PerryLorier | Revert |
@@ -13,8 +13,9 @@
* <tt>HTB: quantum of class XXXXYYYY is big. Consider r2q change.</tt> means class XXXX:YYYY has a massive quantum. quantum by default is the rate of the class, divided by "r2q". http://www.docum.org/docum.org/faq/cache/31.html
* filter...protocol specifies which skb->protocol you're talking about, normally skb->protocol == ethertype. If you don't care you /must/ in some circumstances specify "protocol all". In some situations protocol <i>ethertype</i> works, in some situations it gives an invalid argument.
* The default action of the sfq's internal classifier when a packet doesn't match, is to always put it in bucket 0. These users will get abysmal performance under any kind of load. The "flow" external classifier, when a packet doesn't match, is to drop it all together. These users get 100% packet loss, with or without load. At least the second one is an obvious problem during testing, the first one is often only discovered after users whine.
* <tt>ifb</tt> (Intermediate Functional Block) is a replacement for IMQ. ifb is in the kernel. [ref|http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/net/ifb.c;hb=HEAD]
+* We were getting errors having two rules at the same priority. I think having two u32 rules at the same priority tries to merge them into one hashtable, if this is not possible you get an "invalid argument". Consider using a unique priority/preference for one of the rules and see if that solves the issue.
To match PPPoE discovery ethertype:
<verbatim>
$TC filter add dev $DEV \
