From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: dan@coverfire.com, netdev@vger.kernel.org
Subject: Re: [PATCH] cls_flow: Add tunnel support to the flow classifier
Date: Mon, 24 Oct 2011 18:36:40 -0400 (EDT) [thread overview]
Message-ID: <20111024.183640.270445902457677669.davem@davemloft.net> (raw)
In-Reply-To: <1319428781.2517.26.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Mon, 24 Oct 2011 05:59:41 +0200
> [PATCH net-next] net_sched: cls_flow: use skb_header_pointer()
>
> Dan Siemon would like to add tunnelling support to cls_flow
>
> This preliminary patch introduces use of skb_header_pointer() to help
> this task, while avoiding skb head reallocation because of deep packet
> inspection.
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Applied.
prev parent reply other threads:[~2011-10-24 22:36 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
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 [this message]
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=20111024.183640.270445902457677669.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dan@coverfire.com \
--cc=eric.dumazet@gmail.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;
as well as URLs for NNTP newsgroup(s).