From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 1/3] doc: Add restrictions for ACL rule fields
Date: Wed, 18 Feb 2015 16:28:49 +0000 [thread overview]
Message-ID: <1424276931-16380-2-git-send-email-konstantin.ananyev@intel.com> (raw)
In-Reply-To: <1424276931-16380-1-git-send-email-konstantin.ananyev@intel.com>
Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
---
doc/guides/prog_guide/packet_classif_access_ctrl.rst | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/doc/guides/prog_guide/packet_classif_access_ctrl.rst b/doc/guides/prog_guide/packet_classif_access_ctrl.rst
index 72f4510..e018c68 100644
--- a/doc/guides/prog_guide/packet_classif_access_ctrl.rst
+++ b/doc/guides/prog_guide/packet_classif_access_ctrl.rst
@@ -1,5 +1,5 @@
.. BSD LICENSE
- Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
+ Copyright(c) 2010-2015 Intel Corporation. All rights reserved.
All rights reserved.
Redistribution and use in source and binary forms, with or without
@@ -51,8 +51,18 @@ The library API provides the following basic operations:
Overview
--------
+Rule definition
+~~~~~~~~~~~~~~~
+
The current implementation allows the user for each AC context to specify its own rule (set of fields)
over which packet classification will be performed.
+Though there are few restrictions on the rule fields layout:
+
+* First field in the rule definition has to be one byte long.
+* All subsequent fields has to be grouped into sets of 4 consecutive bytes.
+
+This is done mainly for performance reasons - search function processes the first input byte as part of the flow setup and then the inner loop of the search function is unrolled to process four input bytes at a time.
+
To define each field inside an AC rule, the following structure is used:
.. code-block:: c
@@ -85,10 +95,7 @@ To define each field inside an AC rule, the following structure is used:
A zero-based value that represents the position of the field inside the rule; 0 to N-1 for N fields.
* input_index
- 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.
+ As mentioned above, all input fields, except the very first one, must be in groups of 4 consecutive bytes.
The input index specifies to which input group that field belongs to.
* offset
--
1.8.3.1
next prev parent reply other threads:[~2015-02-18 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 16:28 [dpdk-dev] [PATCH 0/3] doc: ACL - add description for new features Konstantin Ananyev
2015-02-18 16:28 ` Konstantin Ananyev [this message]
2015-02-18 16:28 ` [dpdk-dev] [PATCH 2/3] doc: ACL - add description for different classification methods Konstantin Ananyev
2015-02-18 16:28 ` [dpdk-dev] [PATCH 3/3] doc: ACL - add description for max_size build parameter Konstantin Ananyev
2015-02-18 19:33 ` [dpdk-dev] [PATCH 0/3] doc: ACL - add description for new features Butler, Siobhan A
2015-02-24 3:08 ` Thomas Monjalon
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=1424276931-16380-2-git-send-email-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@intel.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).