From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] trivial 6in4 fix(?)
Date: Sun, 16 Jun 2013 12:19:27 -0700 [thread overview]
Message-ID: <CAA93jw5=ZmFZh_fGLm2t0b3ABrTT9jMwKNDPMAzn3qYv-CvC2A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4JCCtrwU4786kM8a+vjfhm1CaHZOaGKAqLdDOXp=GK9Q@mail.gmail.com>
ok, 3.8.13-7 committed, tagged, and pushed. Sorry about that...
If you could redo that test with simplest.qos or with the
rrul_noclassification test, it would be interesting, then with the
patches, again...
TIA.
On Sun, Jun 16, 2013 at 12:13 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I don't think I pushed out the 6in4 patch into the build. Hell, I
> forgot to tag it too. Remind me to take a vacation next vacation?
>
> If these patches aren't in your build, it looks like we are indeed
> only using one class for fq_codel 6in4 traffic and thus are reverting
> to nearly pure codel behavior rather than fq_codel.
>
> I might be getting good at reading the patterns here - it looks like
> this is fq_codel rather than nfq_codel?
>
> # target/linux/generic/patches-3.8/677-flow_dissector-Add-6in4-support-to-hash-keys.patch
> # target/linux/generic/patches-3.8/678-Handle-encapsulated-ipv6-better.patch
> # target/linux/generic/patches-3.8/678-remove-bad-timeout-logic-in-fast-recovery.patch
>
> as
>
> tc -s class show dev ge00 output during the test seems to show only one or two
> tc classes in use.
>
> But a better test if you are using simplest.qos, rather than
> simplest.qos, would be the 4BE test.
>
> On Sun, Jun 16, 2013 at 11:56 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> Dave Taht <dave.taht@gmail.com> writes:
>>
>>> I am curious: Is there a current user of cero using simplest.qos,
>>> tunneling ipv6 via hurricane or 6to4, that can hammer it with multiple
>>> ipv6 streams (as in the rrul test)? (If you have rrul and ipv6, you
>>> can force it to do pure ipv6 testing with the -6 option.)
>>
>> Attaching a plot of rrul over ipv6 while running cerowrt-3.8.13-17 (or
>> my own build based on it that, is), and some output of tc -s class show
>> dev ge00 while the test was running.
>>
>> IPv4 pings stay flat at 45ms to the same host while the test is running.
>>
>> -Toke
>>
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2013-06-16 19:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 17:13 Dave Taht
2013-06-16 18:56 ` Toke Høiland-Jørgensen
2013-06-16 19:13 ` Dave Taht
2013-06-16 19:19 ` Dave Taht [this message]
2013-06-16 19:21 ` Toke Høiland-Jørgensen
2013-06-16 19:27 ` Dave Taht
2013-06-16 19:36 ` Toke Høiland-Jørgensen
2013-06-16 19:38 ` Toke Høiland-Jørgensen
2013-06-16 20:32 ` Sebastian Moeller
2013-06-16 20:55 ` Toke Høiland-Jørgensen
2013-06-16 20:57 ` Dave Taht
2013-06-16 20:58 ` Toke Høiland-Jørgensen
2013-06-17 7:35 ` Sebastian Moeller
2013-06-17 7:30 ` Sebastian Moeller
2013-06-17 9:44 ` Toke Høiland-Jørgensen
2013-06-17 10:40 ` Sebastian Moeller
2013-06-17 10:50 ` Toke Høiland-Jørgensen
2013-06-17 12:27 ` Sebastian Moeller
2013-07-09 15:06 ` Sebastian Moeller
2013-06-16 19:21 ` Dave Taht
2013-06-16 19:30 ` Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw5=ZmFZh_fGLm2t0b3ABrTT9jMwKNDPMAzn3qYv-CvC2A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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