Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Samudrala, Sridhar <sridhar.samudrala@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] [net-next] net: ixgbe: Extend cls_u32 offload to support UDP headers.
Date: Wed, 09 Mar 2016 21:35:10 -0800	[thread overview]
Message-ID: <56E1078E.4070300@intel.com> (raw)
In-Reply-To: <20160309233215.32377.54007.stgit@sdncamp.jf.intel.com>

On 3/9/2016 3:32 PM, Amritha Nambiar wrote:
> Added support to match on UDP fields in the transport layer.
> Extended core logic to support multiple headers.
>
> Verified with the following filters :
>
> # tc qdisc add dev enp2s0f0 ingress
> # tc filter add dev enp2s0f0 parent ffff: protocol ip prio 99 \
> 	handle 1: u32 divisor 1
> # tc filter add dev enp2s0f0 protocol ip parent ffff: prio 99 \
> 	u32 ht 800: order 1 link 1: \
> 	offset at 0 mask 0f00 shift 6 plus 0 eat match ip protocol 6 ff
> # tc filter add dev enp2s0f0 parent ffff: protocol ip \
> 	u32 ht 1: order 2 \
> 	match tcp src 1024 ffff match tcp dst 23 ffff action drop
> # tc filter add dev enp2s0f0 parent ffff: protocol ip prio 99 \
> 	handle 2: u32 divisor 1
> # tc filter add dev enp2s0f0 protocol ip parent ffff: prio 99 \
> 	u32 ht 800: order 3 link 2: \
> 	offset at 0 mask 0f00 shift 6 plus 0 eat match ip protocol 17 ff
> # tc filter add dev enp2s0f0 parent ffff: protocol ip \
> 	u32 ht 2: order 4 \
> 	match udp src 1025 ffff match udp dst 24 ffff action drop
>
> Signed-off-by: Amritha Nambiar <amritha.nambiar@intel.com>

Acked-by: Sridhar Samudrala <sridhar.samudrala@intel.com>


      parent reply	other threads:[~2016-03-10  5:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 23:32 [Intel-wired-lan] [PATCH] [net-next] net: ixgbe: Extend cls_u32 offload to support UDP headers Amritha Nambiar
2016-03-09 23:36 ` John Fastabend
2016-03-10  5:35 ` Samudrala, Sridhar [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=56E1078E.4070300@intel.com \
    --to=sridhar.samudrala@intel.com \
    --cc=intel-wired-lan@osuosl.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