From: GitHub <noreply@github.com>
To: cerowrt-commits@bufferbloat.net
Subject: [dtaht/Cerowrt-3.3] b8fc8c: Put new sfq flows to head.
Date: Sat, 14 Apr 2012 11:45:25 -0700 [thread overview]
Message-ID: <4f89c5c58562c_6384188fae41435cd@sh2.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/Cerowrt-3.3
Commit: b8fc8ce2c83a97a16e5b188fe6d4ea485b7895e8
https://github.com/dtaht/Cerowrt-3.3/commit/b8fc8ce2c83a97a16e5b188fe6d4ea485b7895e8
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-13 (Fri, 13 Apr 2012)
Changed paths:
A target/linux/ar71xx/patches-3.3/0004-Revert-sch_sfq-revert-dont-put-new-flow-at-the-end-o.patch
Log Message:
-----------
Put new sfq flows to head.
Major conflict between science and engineering here.
Without fiddling with this patch at least a little, coming up with ways
to make it better.
This patch made sfq perform as well as qfq.
And as qfq is busted, and the circumstances under which this bug
occured I was unable to duplicate in cerowrt (I have no doubt it
exists), I'd like to duplicate it and see if fixing htb helps.
Later on.
I will revert this patch if I can create pathological circumstances
with the cerowrt code.
Commit: 34a2314350c9c29473b35bd9163dbee57cff8e2d
https://github.com/dtaht/Cerowrt-3.3/commit/34a2314350c9c29473b35bd9163dbee57cff8e2d
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-13 (Fri, 13 Apr 2012)
Changed paths:
M target/linux/ar71xx/Makefile
Log Message:
-----------
Linux 3.2.2
Compare: https://github.com/dtaht/Cerowrt-3.3/compare/ecb2d93...34a2314
reply other threads:[~2012-04-14 18:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4f89c5c58562c_6384188fae41435cd@sh2.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@bufferbloat.net \
/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