From: GitHub <noreply@github.com>
To: cerowrt-commits@bufferbloat.net
Subject: [dtaht/Cerowrt-3.3] fb0a76: update dnsmasq to head
Date: Thu, 19 Apr 2012 14:21:42 -0700 [thread overview]
Message-ID: <4f9081e6ba148_79961c0caf0505c@sh3.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 3177 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/Cerowrt-3.3
Commit: fb0a760979ecd36656640cc3f81d4e377b4a4bbe
https://github.com/dtaht/Cerowrt-3.3/commit/fb0a760979ecd36656640cc3f81d4e377b4a4bbe
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-18 (Wed, 18 Apr 2012)
Changed paths:
M package/dnsmasq/Makefile
Log Message:
-----------
update dnsmasq to head
SO_BINDTODEVICE fix (I hope)
Commit: 49e8555eddbedd8cd0b3e23b79c971ad9f08824f
https://github.com/dtaht/Cerowrt-3.3/commit/49e8555eddbedd8cd0b3e23b79c971ad9f08824f
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-19 (Thu, 19 Apr 2012)
Changed paths:
A package/iptables/patches/900-packed.patch
Log Message:
-----------
The __packed define leaks up to iptables. Define it properly
Using __packed everywhere leaked up to iptables, so making
sure it's defined everywhere it's called eliminated compile
problems.
Commit: 8b2918c0f56a26241a83f9f6c493da9a457e806c
https://github.com/dtaht/Cerowrt-3.3/commit/8b2918c0f56a26241a83f9f6c493da9a457e806c
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-19 (Thu, 19 Apr 2012)
Changed paths:
A target/linux/ar71xx/patches-3.3/0004-Restore-optional-SFQ-Head-of-Queue-behavior.patch
Log Message:
-----------
The original HoQ behavior for SFQ is superior for home gateways
However it may be unstable under some circumstances yet to be
defined, so there's now a kernel parameter, 'hoq' to turn
it on or off.
Commit: 53cae5fbbf1d5f44ed3dd07cd4d6d7238907226f
https://github.com/dtaht/Cerowrt-3.3/commit/53cae5fbbf1d5f44ed3dd07cd4d6d7238907226f
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-19 (Thu, 19 Apr 2012)
Changed paths:
A target/linux/ar71xx/patches-3.3/923-comprehensive-tcp-udp-ipv6-ipv4-alignment-fixes.patch
Log Message:
-----------
ipv6: Various ipv6 and ipv4 functions threw alignment traps
This is a comprehensive (and somewhat invasive) set of fixes
for the problem. We went from 100k traps a second on ipv6
to .7/sec, and performance more than doubled.
Also, crashes in tunneling stopped.
ipv4: From 33k traps/sec on ipv4 to 8k/sec, and performance
improved by about 30Mbit/sec.
The only traps left are in the aqm code, which ironically
is what we need to exercise most. So fixing those is
next.
Commit: 542d36e9224194300c93c98db7bbd177c9418bb0
https://github.com/dtaht/Cerowrt-3.3/commit/542d36e9224194300c93c98db7bbd177c9418bb0
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-19 (Thu, 19 Apr 2012)
Changed paths:
M package/iptables/Makefile
M target/linux/ar71xx/patches-3.3/0001-Treat-ND-option-31-as-userland-DNSSL-support.patch
R target/linux/ar71xx/patches-3.3/0002-Unaligned-Access-Hacks-for-ar71xx-Architecture.patch
R target/linux/ar71xx/patches-3.3/0003-Some-more-mostly-ipv6-related-alignment-patches.patch
R target/linux/ar71xx/patches-3.3/0004-Revert-sch_sfq-revert-dont-put-new-flow-at-the-end-o.patch
Log Message:
-----------
Cerowrt 3.3.2-6
Compare: https://github.com/dtaht/Cerowrt-3.3/compare/34a2314...542d36e
reply other threads:[~2012-04-19 21:21 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=4f9081e6ba148_79961c0caf0505c@sh3.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