From: <guyk@marvell.com>
To: <orika@nvidia.com>
Cc: <thomas@monjalon.net>, <guyk@marvell.com>, <smadarf@marvell.com>,
<dovrat@marvell.com>, <dev@dpdk.org>, <jerinj@marvell.com>
Subject: [dpdk-dev] [PATCH v1] regexdev: add OOS capability definition
Date: Tue, 20 Oct 2020 11:16:24 +0300 [thread overview]
Message-ID: <20201020081624.25210-1-guyk@marvell.com> (raw)
From: Guy Kaneti <guyk@marvell.com>
Add out of order scan capability to check PMD
support for OOS.
Signed-off-by: Guy Kaneti <guyk@marvell.com>
---
lib/librte_regexdev/rte_regexdev.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/lib/librte_regexdev/rte_regexdev.h b/lib/librte_regexdev/rte_regexdev.h
index 4077e62c9..60cccf816 100644
--- a/lib/librte_regexdev/rte_regexdev.h
+++ b/lib/librte_regexdev/rte_regexdev.h
@@ -474,6 +474,14 @@ rte_regexdev_get_dev_id(const char *name);
* @see RTE_REGEXDEV_CFG_MATCH_ALL_F
*/
+#define RTE_REGEXDEV_CAPA_QUEUE_PAIR_OOS_F (1ULL << 22)
+/**< RegEx device support out of order scan, this means the scan can be retired
+ * as soon as device returns completion.
+ *
+ * @see RTE_REGEX_QUEUE_PAIR_CFG_OOS_F
+ * @see struct rte_regexdev_info::regexdev_capa
+ */
+
/* Enumerates PCRE rule flags */
#define RTE_REGEX_PCRE_RULE_ALLOW_EMPTY_F (1ULL << 0)
/**< When this flag is set, the pattern that can match against an empty string,
--
2.28.0
next reply other threads:[~2020-10-20 8:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 8:16 guyk [this message]
2020-10-20 9:11 ` Ori Kam
2020-10-20 12:37 ` Thomas Monjalon
2020-10-20 14:24 ` [dpdk-dev] [EXT] " Guy Kaneti
2020-10-21 7:15 ` Ori Kam
2020-10-21 7:39 ` Guy Kaneti
2020-10-21 7:53 ` Thomas Monjalon
2020-10-21 8:03 ` [dpdk-dev] [PATCH v2] " guyk
2020-10-21 9:17 ` Ori Kam
2020-10-27 9:19 ` Guy Kaneti
2020-11-03 0:35 ` 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=20201020081624.25210-1-guyk@marvell.com \
--to=guyk@marvell.com \
--cc=dev@dpdk.org \
--cc=dovrat@marvell.com \
--cc=jerinj@marvell.com \
--cc=orika@nvidia.com \
--cc=smadarf@marvell.com \
--cc=thomas@monjalon.net \
/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).