Message ID | 20201217103731.24074-1-orika@nvidia.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 06B26A09F0; Thu, 17 Dec 2020 11:37:44 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D9415C9D6; Thu, 17 Dec 2020 11:37:42 +0100 (CET) Received: from mellanox.co.il (mail-il-dmz.mellanox.com [193.47.165.129]) by dpdk.org (Postfix) with ESMTP id B7BB9C9D2 for <dev@dpdk.org>; Thu, 17 Dec 2020 11:37:41 +0100 (CET) Received: from Internal Mail-Server by MTLPINE1 (envelope-from orika@nvidia.com) with SMTP; 17 Dec 2020 12:37:37 +0200 Received: from MTL-ORIKA.mtl.com ([172.27.14.211]) by labmailer.mlnx (8.13.8/8.13.8) with ESMTP id 0BHAbaVk029627; Thu, 17 Dec 2020 12:37:36 +0200 From: Ori Kam <orika@nvidia.com> To: jerinj@marvell.com Cc: guyk@marvell.com, dev@dpdk.org, thomas@monjalon.net, orika@nvidia.com Date: Thu, 17 Dec 2020 12:37:29 +0200 Message-Id: <20201217103731.24074-1-orika@nvidia.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH 0/2] regexdev: add new response flag X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Series |
regexdev: add new response flag
|
|
Message
Ori Kam
Dec. 17, 2020, 10:37 a.m. UTC
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(-)
Comments
17/12/2020 11:37, Ori Kam: > 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 Applied, thanks.