From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Michal Miroslaw <mirq-linux@rere.qmqm.pl>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] Enable zero verdicts in ACLs
Date: Thu, 19 Jan 2017 11:57:23 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772583F107FA5@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <cover.1484767464.git.mirq-linux@rere.qmqm.pl>
> -----Original Message-----
> From: Michał Mirosław [mailto:mirq-linux@rere.qmqm.pl]
> Sent: Wednesday, January 18, 2017 7:33 PM
> To: dev@dpdk.org
> Cc: Ananyev, Konstantin <konstantin.ananyev@intel.com>; Thomas Monjalon <thomas.monjalon@6wind.com>
> Subject: [PATCH 0/2] Enable zero verdicts in ACLs
>
> This set enables one to have ACL matches return 0 where the distinction
> from no-match case is not needed.
>
> This is a resubmission of the patches as a series, rebased on net-next tree,
> no other changes vs v2.
>
> v2: fixes to prog_guide and ACL tests
>
> Michał Mirosław (2):
> acl: remove invalid test
> acl: allow zero verdict
>
> app/test/test_acl.c | 33 ----------------------
> .../prog_guide/packet_classif_access_ctrl.rst | 3 +-
> lib/librte_acl/rte_acl.c | 3 +-
> lib/librte_acl/rte_acl.h | 2 --
> lib/librte_table/rte_table_acl.c | 2 +-
> 5 files changed, 4 insertions(+), 39 deletions(-)
>
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.11.0
next prev parent reply other threads:[~2017-01-19 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 19:32 Michał Mirosław
2017-01-18 19:32 ` [dpdk-dev] [PATCH 2/2] acl: allow zero verdict Michał Mirosław
2017-01-18 19:32 ` [dpdk-dev] [PATCH 1/2] acl: remove invalid test Michał Mirosław
2017-01-19 11:57 ` Ananyev, Konstantin [this message]
2017-01-30 10:10 ` [dpdk-dev] [PATCH 0/2] Enable zero verdicts in ACLs Thomas Monjalon
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=2601191342CEEE43887BDE71AB9772583F107FA5@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=thomas.monjalon@6wind.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 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).