From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] nftables
Date: Mon, 21 Oct 2013 11:37:14 -0700 [thread overview]
Message-ID: <CAA93jw7uJKYj3Oqaf+kmaFvsUKgf5F2apOeeKc96o7puuimKag@mail.gmail.com> (raw)
I am happy to see a replacement for iptables begin to emerge. There's
lots of cool things about it, and it's my hope the vm is actually fast
enough to use in complex ways. It's generally the "expressibility" of
iptables that makes me bats; it's very difficult to automatically make
efficient rules - a human can generally do much, much better.
But that said: I don't plan to fiddle with it in this release cycle,
nor, probably, the next. It's cool that it's landing in 3.13, but I
would anticipate it taking several releases to shake out enough to
even try out on a non-x86 platform.
At the moment I plan to be on 3.10.X for a long time.
And I'd like to get the "I" out of the paragraphs above and more into a "we".
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2013-10-21 18:37 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
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=CAA93jw7uJKYj3Oqaf+kmaFvsUKgf5F2apOeeKc96o7puuimKag@mail.gmail.com \
--to=dave.taht@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