From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Salter's written a nice article, but missed bufferbloat all the improvements to Linux in CeroWRT
Date: Wed, 20 Jan 2016 15:54:52 +0000 [thread overview]
Message-ID: <569FADCC.4000702@gmail.com> (raw)
In-Reply-To: <1453302261.02626297@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On 20/01/16 15:04, dpreed@reed.com wrote:
>
> http://arstechnica.com/gadgets/2016/01/numbers-dont-lie-its-time-to-build-your-own-router/
>
Definitely a missed opportunity :), many of those nice fast connections
are unfortunately over-buffered.
I think it's interesting in its own right. The 10kB x 100 row is
horrible, and it's not that far-fetched for modern bloated web pages. A
new frontier for the modern speed test :).
My reflex was to ask what's actually being measured. Is it faster with
IPv6 (no NAT)? Would the connection tracking overhead still be
significant? (I also hear Dave screaming about offloads, but I don't
think that's why we see (low-power) Ivy Bridge cpu brought down to only
200mbps of packet forwarding in the last row).
Stateless firewalls should work quite well for TCP, you just drop
incoming SYN. It's connection-less UDP that breaks it. (And often you
still don't need high-volume connection-less, but you want unreliable
datagrams and the network wasn't designed with security in mind...).
[-- Attachment #2: Type: text/html, Size: 1702 bytes --]
next prev parent reply other threads:[~2016-01-20 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 15:04 dpreed
2016-01-20 15:54 ` Alan Jenkins [this message]
2016-01-20 16:11 ` Alan Jenkins
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=569FADCC.4000702@gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=cerowrt-devel@lists.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