DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Mingshan" <mingshan.zhang@intel.com>
To: "Chautru, Nicolas" <nicolas.chautru@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"gakhil@marvell.com" <gakhil@marvell.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"trix@redhat.com" <trix@redhat.com>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"Joshi,  Arun" <arun.joshi@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 6/6] bbdev: reduce warning level for one scenario
Date: Fri, 20 Aug 2021 02:15:48 +0000	[thread overview]
Message-ID: <DM6PR11MB38043B2454320A441B6B377A82C19@DM6PR11MB3804.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1629407410-28822-7-git-send-email-nicolas.chautru@intel.com>

Queue setup may genuinely fail when adding incremental queues for a given priority level. In that case application would attempt to configure a queue at a different priority level.
Not an actual error.

Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
Acked-by: Mingshan Zhang <mingshan.zhang@intel.com>
---
 lib/bbdev/rte_bbdev.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/lib/bbdev/rte_bbdev.c b/lib/bbdev/rte_bbdev.c index fc37236..defddcf 100644
--- a/lib/bbdev/rte_bbdev.c
+++ b/lib/bbdev/rte_bbdev.c
@@ -528,9 +528,10 @@ struct rte_bbdev *
 	ret = dev->dev_ops->queue_setup(dev, queue_id, (conf != NULL) ?
 			conf : &dev_info.default_queue_conf);
 	if (ret < 0) {
-		rte_bbdev_log(ERR,
-				"Device %u queue %u setup failed", dev_id,
-				queue_id);
+		/* This may happen when trying different priority levels */
+		rte_bbdev_log(INFO,
+				"Device %u queue %u setup failed",
+				dev_id, queue_id);
 		return ret;
 	}
 
--
1.8.3.1


  reply	other threads:[~2021-08-20  8:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 21:10 [dpdk-dev] [PATCH v2 0/6] bbdev update related to CRC usage Nicolas Chautru
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 1/6] bbdev: add capability for CRC16 check Nicolas Chautru
2021-09-01 13:36   ` Tom Rix
2021-09-01 15:00     ` Chautru, Nicolas
2021-09-11 19:11       ` Tom Rix
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 2/6] baseband/turbo_sw: add support for CRC16 Nicolas Chautru
2021-09-01 14:00   ` Tom Rix
2021-09-08  0:54     ` Chautru, Nicolas
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 3/6] bbdev: add capability for 4G CB CRC DROP Nicolas Chautru
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 4/6] baseband/acc100: add support for 4G CRC drop Nicolas Chautru
2021-09-01 14:20   ` Tom Rix
2021-09-08  1:04     ` Chautru, Nicolas
2021-09-11 19:13       ` Tom Rix
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 5/6] doc: clarification of usage of HARQ in bbdev doc Nicolas Chautru
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 6/6] bbdev: reduce warning level for one scenario Nicolas Chautru
2021-08-20  2:15   ` Zhang, Mingshan [this message]
2021-09-01 14:29   ` Tom Rix
2021-09-08  1:12     ` Chautru, Nicolas

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=DM6PR11MB38043B2454320A441B6B377A82C19@DM6PR11MB3804.namprd11.prod.outlook.com \
    --to=mingshan.zhang@intel.com \
    --cc=arun.joshi@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=nicolas.chautru@intel.com \
    --cc=thomas@monjalon.net \
    --cc=trix@redhat.com \
    /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).