From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dan Siemon <dan@coverfire.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] cls_flow: Add tunnel support to the flow classifier
Date: Mon, 17 Oct 2011 08:40:23 +0200 [thread overview]
Message-ID: <1318833623.2500.45.camel@edumazet-laptop> (raw)
In-Reply-To: <1318806373.7169.35.camel@ganymede>
Le dimanche 16 octobre 2011 à 19:06 -0400, Dan Siemon a écrit :
> When used on an interface carrying tunneled traffic the flow classifier
> can't look into the tunnels so all of the traffic within the tunnel is
> treated as a single flow. This does not allow any type of intelligent
> queuing to occur. This patch adds new keys to the flow classifier which
> look inside the tunnel. Presently IP-IP, IP-IPv6, IPv6-IPv6 and IPv6-IP
> tunnels are supported.
>
> If you are interested I have posted some background and experimental
> results at:
> http://www.coverfire.com/archives/2011/10/16/making-the-linux-flow-classifier-tunnel-aware/
>
> The related iproute2 patch can be found at the above URL as well.
>
> Signed-off-by: Dan Siemon <dan@coverfire.com>
>
Hi Dan
You're adding a lot of code (omitting the diffstat :( ) for a specific
usage, yet GRE tunnels are not supported.
IPv6 part is also a bit limited : It assumes TCP/UDP headers are the
first ones. Maybe its time to use ipv6_skip_exthdr() ?
Note also that if we pull (with pskb_network_may_pull()) too many bytes,
we kill routing performance on paged frags devices, wich are now
becoming very common.
Adding tunnel support and deep packet inspection might require the use
of skb_header_pointer() wich does the copy of needed data without
requiring expensive reallocation of skb head.
next prev parent reply other threads:[~2011-10-17 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 23:06 [PATCH] cls_flow: Add tunnel support to the flow classifier Dan Siemon
2011-10-17 6:40 ` Eric Dumazet [this message]
2011-10-24 1:21 ` Dan Siemon
2011-10-24 3:14 ` Eric Dumazet
2011-10-24 3:59 ` Eric Dumazet
2011-10-24 22:36 ` David Miller
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=1318833623.2500.45.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=dan@coverfire.com \
--cc=netdev@vger.kernel.org \
/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