From: Ori Kam <orika@nvidia.com>
To: "guyk@marvell.com" <guyk@marvell.com>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"smadarf@marvell.com" <smadarf@marvell.com>,
"dovrat@marvell.com" <dovrat@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"jerinj@marvell.com" <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] regexdev: add OOS capability definition
Date: Wed, 21 Oct 2020 09:17:01 +0000 [thread overview]
Message-ID: <DM6PR12MB49879649D5E548E8E26DB6E3D61C0@DM6PR12MB4987.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201021080332.27463-1-guyk@marvell.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of guyk@marvell.com
> Sent: Wednesday, October 21, 2020 11:04 AM
> Subject: [dpdk-dev] [PATCH v2] regexdev: add OOS capability definition
>
> 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>
> ---
> v2 - fix definition comment
> ---
> lib/librte_regexdev/rte_regexdev.h | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/lib/librte_regexdev/rte_regexdev.h
> b/lib/librte_regexdev/rte_regexdev.h
> index 4077e62c9..000165892 100644
> --- a/lib/librte_regexdev/rte_regexdev.h
> +++ b/lib/librte_regexdev/rte_regexdev.h
> @@ -474,6 +474,15 @@ 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 supports out of order scan.
> + * Out of order scan means the response of a specific job can be returned as
> + * soon as it is ready even if previous jobs on the same queue didn't complete.
> + *
> + * @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
Acked-by: Ori Kam <orika@nvidia.com>
Thanks,
Ori
next prev parent reply other threads:[~2020-10-21 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 8:16 [dpdk-dev] [PATCH v1] " guyk
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 [this message]
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=DM6PR12MB49879649D5E548E8E26DB6E3D61C0@DM6PR12MB4987.namprd12.prod.outlook.com \
--to=orika@nvidia.com \
--cc=dev@dpdk.org \
--cc=dovrat@marvell.com \
--cc=guyk@marvell.com \
--cc=jerinj@marvell.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).