From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com
Cc: thomas@monjalon.net, trix@redhat.com, hemant.agrawal@nxp.com,
mingshan.zhang@intel.com, arun.joshi@intel.com,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [dpdk-dev] [PATCH v3 6/6] bbdev: reduce warning level for one scenario
Date: Tue, 7 Sep 2021 18:15:41 -0700 [thread overview]
Message-ID: <1631063741-28631-7-git-send-email-nicolas.chautru@intel.com> (raw)
In-Reply-To: <1631063741-28631-1-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>
---
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
next prev parent reply other threads:[~2021-09-08 1:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 1:15 [dpdk-dev] [PATCH v3 0/6] bbdev update related to CRC usage Nicolas Chautru
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 1/6] bbdev: add capability for CRC16 check Nicolas Chautru
2021-09-12 12:35 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 2/6] baseband/turbo_sw: add support for CRC16 Nicolas Chautru
2021-09-12 12:38 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 3/6] bbdev: add capability for 4G CB CRC DROP Nicolas Chautru
2021-09-12 12:39 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 4/6] baseband/acc100: add support for 4G CRC drop Nicolas Chautru
2021-09-12 12:42 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 5/6] doc: clarification of usage of HARQ in bbdev doc Nicolas Chautru
2021-09-12 12:44 ` Tom Rix
2021-10-11 20:29 ` Thomas Monjalon
2021-10-11 20:33 ` Chautru, Nicolas
2021-09-08 1:15 ` Nicolas Chautru [this message]
2021-09-12 12:54 ` [dpdk-dev] [PATCH v3 6/6] bbdev: reduce warning level for one scenario Tom Rix
2021-09-13 17:03 ` Chautru, Nicolas
2021-09-13 20:01 ` Tom Rix
2021-10-04 23:40 ` Chautru, Nicolas
2021-10-05 10:05 ` Akhil Goyal
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=1631063741-28631-7-git-send-email-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=arun.joshi@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=mingshan.zhang@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).