From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: optimizing for very small bandwidths with fq_codel better?
Date: Fri, 3 May 2013 08:58:24 +0300 [thread overview]
Message-ID: <16BAF29C-8405-40D4-9B03-EEA4E8033112@gmail.com> (raw)
In-Reply-To: <CAA93jw4D214HZXgY-MbGR9p_Q9Yj_Wyb57CaakPVrgem__kzdw@mail.gmail.com>
On 3 May, 2013, at 1:07 am, Dave Taht wrote:
> 1) I think there's a bug in either the kernel or tc or me on tos matching,
So this works:
tc filter add dev eth2 parent a: protocol ip prio 8 u32 match ip tos 0x2e fc flowid a:b
But this doesn't:
tc filter add dev eth2 parent a: protocol ip prio 10 u32 match ip tos 0x08 0xfc flowid a:b
I notice, near the end, that one has fc and the other has 0xfc.
- Jonathan Morton
next prev parent reply other threads:[~2013-05-03 5:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 22:07 Dave Taht
2013-05-03 5:01 ` [Cerowrt-devel] " Mikael Abrahamsson
2013-05-03 11:45 ` Dave Taht
2013-05-03 5:58 ` Jonathan Morton [this message]
2013-05-03 16:53 ` Juliusz Chroboczek
2013-05-03 22:15 ` Dave Taht
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=16BAF29C-8405-40D4-9B03-EEA4E8033112@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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