From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] a bit of kernel hacking for ipv6 encapsulation on skb_flow_dissector?
Date: Tue, 28 May 2013 06:18:10 -0700 [thread overview]
Message-ID: <CAA93jw6=szLySKD4X5jxZ+uPQU84grRuSrvmSxV0oi3q7JNSRg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
I have been fiddling with WAY too many things simultaneously. At the
moment, for example, I'm poking into why transmission doesn't successfully
set the tos field on utp packets while waiting for a profile enabled build
for the tplink while doing a bunch of other things.
... anyway...
While doing that I saw that fq_codel's treatment of IPv6 through a 6in4
tunnel didn't appear to be doing the "right thing", that ipv4 was
outcompeting it left and right.
It looks like the skb_flow_dissector doesn't "do the right thing" on proto
41 (6in4), where it should peel off the ipv4 header and look inside it for
the ipv6 5 tuple. It does do the right thing for GRE... anybody want to
take a stab at fixing
net/core/flow_dissector.c ?
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 997 bytes --]
reply other threads:[~2013-05-28 13:18 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='CAA93jw6=szLySKD4X5jxZ+uPQU84grRuSrvmSxV0oi3q7JNSRg@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