From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A443CA00E6 for ; Sun, 7 Jul 2019 11:43:57 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E5A56322C; Sun, 7 Jul 2019 11:43:55 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 9E25931FC for ; Sun, 7 Jul 2019 11:43:54 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 207F3A0613; Sun, 7 Jul 2019 11:43:54 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Sun, 07 Jul 2019 09:43:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: other X-Bugzilla-Version: 18.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ido@cgstowernetworks.com X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 307] ACL (librte_acl) field of type RANGE and size U32 is not working properly X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D307 Bug ID: 307 Summary: ACL (librte_acl) field of type RANGE and size U32 is not working properly Product: DPDK Version: 18.11 Hardware: All OS: All Status: CONFIRMED Severity: normal Priority: Normal Component: other Assignee: dev@dpdk.org Reporter: ido@cgstowernetworks.com Target Milestone: --- Created attachment 47 --> https://bugs.dpdk.org/attachment.cgi?id=3D47&action=3Dedit acl-test for single field match - can be compiled like any dpdk/example Hi, Such ACL field doesn't seem to work properly=20 ~~~ { .type =3D RTE_ACL_FIELD_TYPE_RANGE, .size =3D sizeof(uint32_t), ... } ~~~ I found same complain here https://mails.dpdk.org/archives/users/2017-June/002096.html (by Doohwan Lee) with no resolution. Also all DPDK ACL test/examples RTE_ACL_FIELD_TYPE_RANGE fields are with uint16_t and never with uint32_t Attached is a small acl-test app=20 It sets a single ACL field (though there are few in the acl_fields array all the rest are don't-care) And matches a data argument (no need for traffic/packets) usage: ~~~ ./acl-test [EAL options] -- [app options] app options: --size=3D16|32 [--type=3DRANGE --min=3D --max=3D] [--type=3DBITMASK --value=3D --bitmask=3D] --data=3D example: ./acl-test --no-huge -c 1 -- --size=3D32 --type=3DRANGE --min=3D100= --max=3D200 --data=3D150 ~~~ Output example for RANGE U16 ~~~ cgs@ubuntu:~/workspace/KAZ/output/build/arpeggio/host/dpdk/app$ ./acl-test --no-huge -c 1 -- --size=3D16 --type=3DRANGE --min=3D1 --max=3D500 --data= =3D250 EAL: Detected 4 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /run/user/1000/dpdk/rte/mp_socket EAL: Probing VFIO support... EAL: Started without hugepages support, physical addresses not available EAL: PCI device 0000:02:01.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:100f net_e1000_em EAL: PCI device 0000:02:06.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:100f net_e1000_em RULE 1: | 00/00 | 0001/01F4 0000/0000 | 00000000/FFFFFFFF | 00000000/00000000 | 0x1-0x1-0x1=20 acl context @0x7f9dede13b40 socket_id=3D0 alg=3D3 max_rules=3D256 rule_size=3D96 num_rules=3D1 num_categories=3D1 num_tries=3D1 250 is in range 1-500 should MATCH ACL MATCH test PASSED ~~~ Bad output example for RANGE U32 (same test just size change) ~~~ ./acl-test --no-huge -c 1 -- --size=3D32 --type=3DRANGE --min=3D1 --max=3D5= 00 --data=3D250 EAL: Detected 4 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /run/user/1000/dpdk/rte/mp_socket EAL: Probing VFIO support... EAL: Started without hugepages support, physical addresses not available EAL: PCI device 0000:02:01.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:100f net_e1000_em EAL: PCI device 0000:02:06.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:100f net_e1000_em RULE 1: | 00/00 | 0000/FFFF 0000/0000 | 00000001/000001F4 | 00000000/00000000 | 0x1-0x1-0x1=20 acl context @0x7ff3d08a3b40 socket_id=3D0 alg=3D3 max_rules=3D256 rule_size=3D96 num_rules=3D1 num_categories=3D1 num_tries=3D1 250 is in range 1-500 should MATCH ACL NO-MATCH test FAILED! ~~~ Thanx, - Ido --=20 You are receiving this mail because: You are the assignee for the bug.=