From: Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
To: dev@dpdk.org
Cc: Chao Zhu <chaozhu@linux.vnet.ibm.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
pradeep@us.ibm.com
Subject: [dpdk-dev] [PATCH 0/6] enable lpm, acl and other missing libraries in ppc64le
Date: Thu, 7 Jul 2016 08:27:50 +0530 [thread overview]
Message-ID: <1467860276-22848-1-git-send-email-gowrishankar.m@linux.vnet.ibm.com> (raw)
This patchset enables LPM, ACL and other few missing libs in ppc64le and also
address few patches in related examples (ip_pipeline and l3fwd).
Test report:
LPM autotest test results as below.
RTE>>lpm_autotest
No. routes = 1076806
Route distribution per prefix width:
DEPTH QUANTITY (PERCENT)
---------------------------
01 0 (0.00)
02 0 (0.00)
03 1 (0.00)
04 0 (0.00)
05 3 (0.00)
06 2 (0.00)
07 4 (0.00)
08 201 (0.02)
09 37 (0.00)
10 55 (0.01)
11 97 (0.01)
12 381 (0.04)
13 775 (0.07)
14 2104 (0.20)
15 3712 (0.34)
16 69319 (6.44)
17 12983 (1.21)
18 23667 (2.20)
19 69068 (6.41)
20 62354 (5.79)
21 48531 (4.51)
22 72355 (6.72)
23 85427 (7.93)
24 583900 (54.23)
25 2654 (0.25)
26 5650 (0.52)
27 6467 (0.60)
28 7127 (0.66)
29 12936 (1.20)
30 5999 (0.56)
31 13 (0.00)
32 984 (0.09)
Unique added entries = 1039948
Used table 24 entries = 11343198 (67.6107%)
64 byte Cache entries used = 360735 (23087040 bytes)
Average LPM Add: 110766 cycles
Average LPM Lookup: 34.5 cycles (fails = 19.3%)
BULK LPM Lookup: 31.5 cycles (fails = 19.3%)
LPM LookupX4: 29.5 cycles (fails = 19.3%)
Average LPM Delete: 63813.8 cycles
Test OK
RTE>>
ACL autotest test results as below:
......
...
ACL: trie 0: number of rules: 17, indexes: 4
ACL: trie 1: number of rules: 10, indexes: 5
ACL: Gen phase for ACL "acl_ctx":
runtime memory footprint on socket -1:
single nodes/bytes used: 8822/70576
quad nodes/vectors/bytes used: 12788/53374/426992
DFA nodes/group64/bytes used: 2175/4359/2233864
match nodes/bytes used: 24100/3084800
total: 5818432 bytes
max limit: 18446744073709551615 bytes
ACL: Build phase for ACL "acl_ctx":
node limit for tree split: 16384
nodes created: 47885
memory consumed: 100663380
ACL: trie 0: number of rules: 22, indexes: 5
ACL: trie 1: number of rules: 5, indexes: 5
Test OK
RTE>>
Thanks.
next reply other threads:[~2016-07-07 2:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 2:57 Gowrishankar [this message]
2016-07-07 2:57 ` [dpdk-dev] [PATCH 1/6] config: enable lpm, port, table, pipeline, acl, sched libraries for ppc64le Gowrishankar
2016-07-08 12:57 ` Thomas Monjalon
2016-07-09 14:38 ` gowrishankar
2016-07-09 20:53 ` Thomas Monjalon
2016-07-07 2:57 ` [dpdk-dev] [PATCH 2/6] lpm: add altivec intrinsics for dpdk lpm on ppc_64 Gowrishankar
2016-07-07 2:57 ` [dpdk-dev] [PATCH 3/6] acl: add altivec intrinsics for dpdk acl " Gowrishankar
2016-07-07 2:57 ` [dpdk-dev] [PATCH 4/6] table: cache align rte_bucket_4_8 Gowrishankar
2016-07-07 2:57 ` [dpdk-dev] [PATCH 5/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64 Gowrishankar
2016-07-07 2:57 ` [dpdk-dev] [PATCH 6/6] l3fwd: add altivec support for em_hash_key Gowrishankar
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=1467860276-22848-1-git-send-email-gowrishankar.m@linux.vnet.ibm.com \
--to=gowrishankar.m@linux.vnet.ibm.com \
--cc=bruce.richardson@intel.com \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=pradeep@us.ibm.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).