From: Ciara Power <ciara.power@intel.com>
To: bruce.richardson@intel.com
Cc: dev@dpdk.org, Ciara Power <ciara.power@intel.com>
Subject: [dpdk-dev] [PATCH 1/2] raw/ioat: fix rawdev state to stopped after test
Date: Thu, 10 Oct 2019 13:36:02 +0100 [thread overview]
Message-ID: <20191010123603.58007-2-ciara.power@intel.com> (raw)
In-Reply-To: <20191010123603.58007-1-ciara.power@intel.com>
The ioat rawdev was initially started during the test, however was never
stopped. This would cause issues when running the test again, as the device
cannot be configured when in a running state.
The device is now stopped after the test has completed, or if the test is
terminated due to error.
Fixes: 849470d522ed ("raw/ioat: add configure, start and stop functions")
Cc: bruce.richardson@intel.com
Signed-off-by: Ciara Power <ciara.power@intel.com>
---
drivers/raw/ioat/ioat_rawdev_test.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/raw/ioat/ioat_rawdev_test.c b/drivers/raw/ioat/ioat_rawdev_test.c
index f6c7dbb80..6aad79486 100644
--- a/drivers/raw/ioat/ioat_rawdev_test.c
+++ b/drivers/raw/ioat/ioat_rawdev_test.c
@@ -220,6 +220,7 @@ ioat_rawdev_test(uint16_t dev_id)
}
printf("\n");
+ rte_rawdev_stop(dev_id);
rte_mempool_free(pool);
free(snames);
free(stats);
@@ -227,6 +228,7 @@ ioat_rawdev_test(uint16_t dev_id)
return 0;
err:
+ rte_rawdev_stop(dev_id);
rte_mempool_free(pool);
free(snames);
free(stats);
--
2.17.1
next prev parent reply other threads:[~2019-10-10 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 12:36 [dpdk-dev] [PATCH 0/2] enable ioat test to run multiple times Ciara Power
2019-10-10 12:36 ` Ciara Power [this message]
2019-10-10 12:40 ` [dpdk-dev] [PATCH 1/2] raw/ioat: fix rawdev state to stopped after test Bruce Richardson
2019-10-10 12:36 ` [dpdk-dev] [PATCH 2/2] raw/ioat: fix initial ring size check Ciara Power
2019-10-10 12:40 ` Bruce Richardson
2019-10-27 13:22 ` [dpdk-dev] [PATCH 0/2] enable ioat test to run multiple times David Marchand
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=20191010123603.58007-2-ciara.power@intel.com \
--to=ciara.power@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).