From: 志昌余 <yuzhichang_scl@hotmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ACL lookup doesn't work for some schemes
Date: Sun, 15 Feb 2015 17:29:51 +0800 [thread overview]
Message-ID: <SNT153-W36B1758C1945C0DFAEB03FF8210@phx.gbl> (raw)
In-Reply-To: <SNT153-W6944A3573097FCF2EE79BF8210@phx.gbl>
I tested against DPDK 1.7.0, 1.8.0 and trunk( ed2547b6).
________________________________
> From: yuzhichang_scl@hotmail.com
> To: dev@dpdk.org
> Subject: RE: ACL lookup doesn't work for some schemes
> Date: Sun, 15 Feb 2015 17:23:53 +0800
>
> Sorry I forgot to attach the sample code in previous mail. See the attached.
>
> ________________________________
> From: yuzhichang_scl@hotmail.com
> To: dev@dpdk.org
> Subject: ACL lookup doesn't work for some schemes
> Date: Sun, 15 Feb 2015 17:18:55 +0800
>
> Hi,
> I noticed that ACL lookup doesn't work for some schemes.
> 1. If the first field is not uint8_t, even all fields are wildcard,
> lookup doesn't find the matching rule. See acl_8last.c.
> 2. I prepended a uint8_t field, keep other fields be wildcard, lookup
> returns the correct result. See acl_8last2.c
> 3. Then I change last field from 8bitmask_WILDCARD to 8bitmask(1, 0x1)
> (matches odd numbers) or 8bitmask(0, 0x1) (match even numbers), lookup
> doesn't return the correct. See acl_8last3.c. And I noticed the
> similar behavior for uint16_t ranges(date doesn't match 0-0x8000 nor
> 0x8001-0xffff).
> Above behaviors are tricky. Does ACL do some
> undocumented assumptions or the table schema?
> Regards,
> Zhichang Yu
next prev parent reply other threads:[~2015-02-15 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 9:18 志昌余
2015-02-15 9:23 ` 志昌余
2015-02-15 9:29 ` 志昌余 [this message]
2015-02-16 9:56 ` Ananyev, Konstantin
2015-02-16 15:37 ` Stevan Markovic
[not found] ` <D1077203.3B62D%smarkovi@akamai.com>
2015-02-16 16:08 ` Ananyev, Konstantin
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=SNT153-W36B1758C1945C0DFAEB03FF8210@phx.gbl \
--to=yuzhichang_scl@hotmail.com \
--cc=dev@dpdk.org \
/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).