From: Erik Ziegenbalg <eziegenb@Brocade.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] rte_acl test-acl app
Date: Fri, 24 Oct 2014 20:15:13 -0700 [thread overview]
Message-ID: <EDD8E64855FBDA45ACDFE02112E795B70A5D6270D6@HQ1-EXCH03.corp.brocade.com> (raw)
Hi everyone,
I am having trouble to successfully perform a packet classification
using the rte_acl test app. I have my rules.acl and trace.acl files as
follows:
rules.acl:
@192.168.0.0/24 192.168.0.0/24 400 : 500 1000 : 2000 6/0xff
trace.acl:
192.168.0.5 192.168.0.9 450 1002 0x06
However, the result always comes up as 4294967295 (xFFFFFFFF). I have
dug through the code quite a bit to follow and see what is going on, but
not sure where I went wrong.
Any help on how the rte_acl_classify function works would be much
appreciated. In understand that the data for rte_acl_classify is a
uint32_t ** and I double checked to make sure I'm passing along proper
values. Is xFFFFFFFF the expected result? If so, I am getting the same
for packets that should not match.
Thank you,
Erik Ziegenbalg
next reply other threads:[~2014-10-25 3:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 3:15 Erik Ziegenbalg [this message]
2014-10-25 3:19 Erik Ziegenbalg
2014-10-28 11:51 ` 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=EDD8E64855FBDA45ACDFE02112E795B70A5D6270D6@HQ1-EXCH03.corp.brocade.com \
--to=eziegenb@brocade.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).