From: Stevan Markovic <smarkovic@prolexic.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"yuzhichang_scl@hotmail.com" <yuzhichang_scl@hotmail.com>
Subject: Re: [dpdk-dev] ACL lookup doesn't work for some schemes
Date: Mon, 16 Feb 2015 10:37:38 -0500 [thread overview]
Message-ID: <CAAmzY8i5nzsMmOef2rqfti9DQvC_1dGoTMukmEXqhiBnOnEpxA@mail.gmail.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258213EC8FE@irsmsx105.ger.corp.intel.com>
Hi,
On Mon, Feb 16, 2015 at 4:56 AM, Ananyev, Konstantin <
konstantin.ananyev@intel.com> wrote:
> Yes, right now, libtre_acl to work correctly first field has to be 1B long
> and all subsequent grouped into sets of 4 consecutive bytes.
> I thought we have it documented into our PG, ACL section:
> http://dpdk.org/doc/guides/prog_guide/packet_classif_access_ctrl.html
> Though re-reading it again:
> "For performance reasons, the inner loop of the search function is
> unrolled to process four input bytes at a time. This requires the input to
> be grouped into sets of 4 consecutive bytes. The loop processes the first
> input byte as part of the setup and then subsequent bytes must be in groups
> of 4 consecutive bytes."
> It probably not very clear and need to be explained in more details.
> Will update the doc.
>
> Konstantin
>
>
While improving API documentation would be great, enforcing these
constraints on user defined fields in rte_acl_build(?) also (return an
error if constraints are not met) would be even better.
Stevan
next prev parent reply other threads:[~2015-02-16 15:37 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 ` 志昌余
2015-02-16 9:56 ` Ananyev, Konstantin
2015-02-16 15:37 ` Stevan Markovic [this message]
[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=CAAmzY8i5nzsMmOef2rqfti9DQvC_1dGoTMukmEXqhiBnOnEpxA@mail.gmail.com \
--to=smarkovic@prolexic.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=yuzhichang_scl@hotmail.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).