From: Gage Eads <gage.eads@intel.com>
To: dev@dpdk.org
Cc: jerin.jacob@caviumnetworks.com, harry.van.haaren@intel.com
Subject: [dpdk-dev] [PATCH 3/3] test/eventdev: fix bug in port enqueue depth test
Date: Wed, 20 Sep 2017 10:21:03 -0500 [thread overview]
Message-ID: <1505920863-14826-4-git-send-email-gage.eads@intel.com> (raw)
In-Reply-To: <1505920863-14826-1-git-send-email-gage.eads@intel.com>
The enqueue depth test was comparing the port's dequeue depth against its
enqueue depth.
Fixes: 410c5bccdadc ("eventdev: add port attribute function")
Signed-off-by: Gage Eads <gage.eads@intel.com>
---
test/test/test_eventdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test/test/test_eventdev.c b/test/test/test_eventdev.c
index 5fd0357..0e8bd7d 100644
--- a/test/test/test_eventdev.c
+++ b/test/test/test_eventdev.c
@@ -649,7 +649,7 @@ test_eventdev_port_attr_enqueue_depth(void)
TEST_ASSERT_EQUAL(rte_event_port_attr_get(TEST_DEV_ID, 0,
RTE_EVENT_PORT_ATTR_ENQ_DEPTH, &value),
0, "Call to get port enqueue depth failed");
- TEST_ASSERT_EQUAL(value, pconf.dequeue_depth,
+ TEST_ASSERT_EQUAL(value, pconf.enqueue_depth,
"Wrong port enqueue depth");
return TEST_SUCCESS;
--
2.7.4
next prev parent reply other threads:[~2017-09-20 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 15:21 [dpdk-dev] [PATCH 0/3] Extend port and queue attribute get functions Gage Eads
2017-09-20 15:21 ` [dpdk-dev] [PATCH 1/3] eventdev: extend queue attribute get function Gage Eads
2017-09-20 15:21 ` [dpdk-dev] [PATCH 2/3] eventdev: extend port " Gage Eads
2017-09-20 15:21 ` Gage Eads [this message]
2017-10-04 14:12 ` [dpdk-dev] [PATCH 0/3] Extend port and queue attribute get functions Van Haaren, Harry
2017-10-08 13:53 ` Jerin Jacob
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=1505920863-14826-4-git-send-email-gage.eads@intel.com \
--to=gage.eads@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jerin.jacob@caviumnetworks.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).