From: "Cao, Waterman" <waterman.cao@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCHv2 0/5] ACL library
Date: Fri, 6 Jun 2014 05:54:46 +0000 [thread overview]
Message-ID: <AA3F441F262C58498CD6D0C1801DE7EB0AA8E990@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1401305210-10357-1-git-send-email-konstantin.ananyev@intel.com>
Tested-by: Waterman Cao <waterman.cao@intel.com>
This patch has been tested by Intel.
Basic functional test has been performed about 'l3fwd-acl', all cases are passed.
It includes test_l3fwdacl_acl_rule, test_l3fwdacl_exact_route, test_l3fwdacl_lpm_route, test_l3fwdAcl_Scalar and test_l3fwdacl_invalid.
There is one known issue about 'acl rule problem with protocol', Konstantin will apply one minor patch to fix it later.
Test Environment:
Fedora 20 x86_64, Linux Kernel 3.11.10-301, GCC 4.8.2 Intel Xeon CPU E5-2680 v2 @ 2.80GHz
next prev parent reply other threads:[~2014-06-06 5:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 19:26 Konstantin Ananyev
2014-05-28 19:26 ` [dpdk-dev] [PATCHv2 1/5] acl: Add ACL library (librte_acl) into DPDK Konstantin Ananyev
2014-05-28 19:26 ` [dpdk-dev] [PATCHv2 2/5] acl: update UT to reflect latest changes in the librte_acl Konstantin Ananyev
2014-05-28 19:26 ` [dpdk-dev] [PATCHv2 3/5] acl: New test-acl application Konstantin Ananyev
2014-05-28 19:26 ` [dpdk-dev] [PATCHv2 4/5] acl: New sample l3fwd-acl Konstantin Ananyev
2014-05-28 19:26 ` [dpdk-dev] [PATCHv2 5/5] acl: add doxygen configuration and start page Konstantin Ananyev
2014-06-06 5:54 ` Cao, Waterman [this message]
2014-06-06 8:32 ` [dpdk-dev] [PATCHv2 0/5] ACL library De Lara Guarch, Pablo
2014-06-11 22:01 ` 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=AA3F441F262C58498CD6D0C1801DE7EB0AA8E990@SHSMSX103.ccr.corp.intel.com \
--to=waterman.cao@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--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).