DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ophir Munk <ophirmu@nvidia.com>
To: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
	Ori Kam <orika@nvidia.com>
Cc: Ophir Munk <ophirmu@nvidia.com>
Subject: [dpdk-dev] [PATCH v1] regex/mlx5: add out of order scan capability
Date: Wed, 28 Oct 2020 13:18:58 +0000	[thread overview]
Message-ID: <20201028131858.25879-1-ophirmu@nvidia.com> (raw)

Add missing out of order scan capability
RTE_REGEXDEV_CAPA_QUEUE_PAIR_OOS_F to mlx5 regex PMD.

Signed-off-by: Ophir Munk <ophirmu@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
---
Depends-on: patch-81673 ("regexdev: add OOS capability definition") `
Depends-on: patch-81509 ("app/regex: configure qp according to device capabilities")

 drivers/regex/mlx5/mlx5_rxp.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/regex/mlx5/mlx5_rxp.c b/drivers/regex/mlx5/mlx5_rxp.c
index b8fab79..7936a52 100644
--- a/drivers/regex/mlx5/mlx5_rxp.c
+++ b/drivers/regex/mlx5/mlx5_rxp.c
@@ -116,7 +116,8 @@ mlx5_regex_info_get(struct rte_regexdev *dev __rte_unused,
 	info->max_rules_per_group = MLX5_REGEX_MAX_RULES_PER_GROUP;
 	info->max_groups = MLX5_REGEX_MAX_GROUPS;
 	info->max_queue_pairs = 1;
-	info->regexdev_capa = RTE_REGEXDEV_SUPP_PCRE_GREEDY_F;
+	info->regexdev_capa = RTE_REGEXDEV_SUPP_PCRE_GREEDY_F |
+			      RTE_REGEXDEV_CAPA_QUEUE_PAIR_OOS_F;
 	info->rule_flags = 0;
 	info->max_queue_pairs = 10;
 	return 0;
-- 
2.8.4


             reply	other threads:[~2020-10-28 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 13:18 Ophir Munk [this message]
2020-11-03  0:37 ` 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=20201028131858.25879-1-ophirmu@nvidia.com \
    --to=ophirmu@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.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).