DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Rapelly, Varun" <vrapelly@sonusnet.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ACL trie insertion and search
Date: Wed, 28 Jan 2015 11:11:12 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258213E0099@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <BLUPR03MB2643C2D0933F868AFD26470B7330@BLUPR03MB264.namprd03.prod.outlook.com>

Hi

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Rapelly, Varun
> Sent: Wednesday, January 28, 2015 9:07 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] ACL trie insertion and search
> 
> Hi,
> 
> We were converting the acl rule data, from host to network byte order, [by mistake] while inserting into trie. And while searching we
> are not converting the search data to n/w byte order.
> With the above also rules are matching, except few scenarios.
> 
> After correcting the above mistake, all rules are matching perfectly fine.
> 
> I believe the above[converting while insertion] should also work for all rules. Please clarify the above.

Yes, that's correct.
rte_acl_add_rules() expects all fields to be in host byte order, while
rte_acl_classify()expects all fields in input data buffers to be in network byte order.
As mentioned in comments in rte_acl.h.  

Konstantin

> 
> Regards,
> Varun

      reply	other threads:[~2015-01-28 11:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28  9:07 Rapelly, Varun
2015-01-28 11:11 ` Ananyev, Konstantin [this message]

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=2601191342CEEE43887BDE71AB977258213E0099@irsmsx105.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.com \
    --cc=dev@dpdk.org \
    --cc=vrapelly@sonusnet.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).