DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ori Kam <orika@nvidia.com>
To: jerinj@marvell.com
Cc: guyk@marvell.com, dev@dpdk.org, thomas@monjalon.net, orika@nvidia.com
Subject: [dpdk-dev] [PATCH 0/2] regexdev: add new response flag
Date: Thu, 17 Dec 2020 12:37:29 +0200	[thread overview]
Message-ID: <20201217103731.24074-1-orika@nvidia.com> (raw)

The RegEx engine is using HW resources that may reach some limit for
different reasons.
In current API the RegEx can report only on max threads reached.

This commit introduce a new flag to report to the app that some
HW resource limit has been reached.


Ori Kam (2):
  regexdev: add resource limit reached rsp flag
  regex/mlx5: add regex response flags

 drivers/regex/mlx5/mlx5_regex_fastpath.c | 23 ++++++++++++++++++++++-
 lib/librte_regexdev/rte_regexdev.h       |  5 +++++
 2 files changed, 27 insertions(+), 1 deletion(-)

-- 
2.25.1


             reply	other threads:[~2020-12-17 10:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 10:37 Ori Kam [this message]
2020-12-17 10:37 ` [dpdk-dev] [PATCH 1/2] regexdev: add resource limit reached rsp flag Ori Kam
2021-01-07 15:16   ` Ori Kam
2020-12-17 10:37 ` [dpdk-dev] [PATCH 2/2] regex/mlx5: add regex response flags Ori Kam
2021-01-12 22:33 ` [dpdk-dev] [PATCH 0/2] regexdev: add new response flag 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=20201217103731.24074-1-orika@nvidia.com \
    --to=orika@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=guyk@marvell.com \
    --cc=jerinj@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).