From: Stephen Hemminger <stephen@networkplumber.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, yotamg@mellanox.com, eladr@mellanox.com,
idosch@mellanox.com, nogahf@mellanox.com, ogerlitz@mellanox.com
Subject: Re: [patch iproute2 1/2] tc: Add support for the matchall traffic classifier.
Date: Mon, 29 Aug 2016 11:03:21 -0700 [thread overview]
Message-ID: <20160829110321.78959dc8@xeon-e3> (raw)
In-Reply-To: <1471866986-3156-2-git-send-email-jiri@resnulli.us>
On Mon, 22 Aug 2016 13:56:25 +0200
Jiri Pirko <jiri@resnulli.us> wrote:
> From: Yotam Gigi <yotamg@mellanox.com>
>
> The matchall classifier matches every packet and allows the user to apply
> actions on it. In addition, it supports the skip_sw and skip_hw (as can
> be found on u32 and flower filter) that direct the kernel to skip the
> software/hardware processing of the actions.
>
> This filter is very useful in usecases where every packet should be
> matched. For example, packet mirroring (SPAN) can be setup very easily
> using that filter.
>
> Signed-off-by: Yotam Gigi <yotamg@mellanox.com>
> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
I am not a checkpatch purist, but these two should be addressed.
WARNING: unnecessary whitespace before a quoted newline
#81: FILE: tc/f_matchall.c:29:
+ fprintf(stderr, "Usage: ... matchall [skip_sw | skip_hw] \n");
WARNING: braces {} are not necessary for single statement blocks
#185: FILE: tc/f_matchall.c:133:
+ if (tb[TCA_MATCHALL_ACT]) {
+ tc_print_action(f, tb[TCA_MATCHALL_ACT]);
+ }
next prev parent reply other threads:[~2016-08-29 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 11:56 [patch iproute2 0/2] Add matchall support to tc Jiri Pirko
2016-08-22 11:56 ` [patch iproute2 1/2] tc: Add support for the matchall traffic classifier Jiri Pirko
2016-08-29 18:03 ` Stephen Hemminger [this message]
2016-08-29 18:40 ` Jiri Pirko
2016-08-22 11:56 ` [patch iproute2 2/2] tc: man: Add man entry for the matchall classifier Jiri Pirko
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=20160829110321.78959dc8@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=eladr@mellanox.com \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=nogahf@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=yotamg@mellanox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.