public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@redhat•com>
To: Paul Blakey <paulb@mellanox•com>
Cc: Stephen Hemminger <stephen@networkplumber•org>,
	netdev@vger•kernel.org, Jiri Pirko <jiri@mellanox•com>,
	Or Gerlitz <ogerlitz@mellanox•com>, Roi Dayan <roid@mellanox•com>,
	Simon Horman <simon.horman@netronome•com>
Subject: Re: [PATCH iproute2 net-next V5] tc: flower: Refactor matching flags to be more user friendly
Date: Thu, 19 Jan 2017 15:48:17 +0100	[thread overview]
Message-ID: <20170119154817.26240372@griffin> (raw)
In-Reply-To: <1484836073-47019-1-git-send-email-paulb@mellanox.com>

On Thu, 19 Jan 2017 16:27:53 +0200, Paul Blakey wrote:
> Instead of "magic numbers" we can now specify each flag
> by name. Prefix of "no"  (e.g nofrag) unsets the flag,
> otherwise it wil be set.
> 
> Example:
>     # add a flower filter that will drop fragmented packets
>     tc filter add dev ens4f0 protocol ip parent ffff: \
>             flower \
>             src_mac e4:1d:2d:fd:8b:01 \
>             dst_mac e4:1d:2d:fd:8b:02 \
>             indev ens4f0 \
>             ip_flags frag \
>     action drop
> 
>     # add a flower filter that will drop non-fragmented packets
>     tc filter add dev ens4f0 protocol ip parent ffff: \
>             flower \
>             src_mac e4:1d:2d:fd:8b:01 \
>             dst_mac e4:1d:2d:fd:8b:02 \
>             indev ens4f0 \
>             ip_flags nofrag \
>     action drop
> 
> Fixes: 22a8f019891c ('tc: flower: support matching flags')
> Signed-off-by: Paul Blakey <paulb@mellanox•com>
> Reviewed-by: Roi Dayan <roid@mellanox•com>

Reviewed-by: Jiri Benc <jbenc@redhat•com>

  reply	other threads:[~2017-01-19 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 14:27 [PATCH iproute2 net-next V5] tc: flower: Refactor matching flags to be more user friendly Paul Blakey
2017-01-19 14:48 ` Jiri Benc [this message]
2017-01-19 14:53 ` Or Gerlitz
2017-01-20 18:38 ` Stephen Hemminger

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=20170119154817.26240372@griffin \
    --to=jbenc@redhat$(echo .)com \
    --cc=jiri@mellanox$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=ogerlitz@mellanox$(echo .)com \
    --cc=paulb@mellanox$(echo .)com \
    --cc=roid@mellanox$(echo .)com \
    --cc=simon.horman@netronome$(echo .)com \
    --cc=stephen@networkplumber$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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