From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"harry.van.haaren@intel.com" <harry.van.haaren@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Subject: [dpdk-dev] [PATCH 3/3] app/eventdev: follow proper teardown sequence
Date: Fri, 1 Mar 2019 07:16:47 +0000 [thread overview]
Message-ID: <20190301071617.6570-3-pbhagavatula@marvell.com> (raw)
In-Reply-To: <20190301071617.6570-1-pbhagavatula@marvell.com>
From: Pavan Nikhilesh <pbhagavatula@marvell.com>
Stop eventdev before closing it.
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
app/test-eventdev/test_pipeline_common.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/app/test-eventdev/test_pipeline_common.c b/app/test-eventdev/test_pipeline_common.c
index 5db3ffde1..1e525643d 100644
--- a/app/test-eventdev/test_pipeline_common.c
+++ b/app/test-eventdev/test_pipeline_common.c
@@ -396,6 +396,7 @@ pipeline_eventdev_destroy(struct evt_test *test, struct evt_options *opt)
{
RTE_SET_USED(test);
+ rte_event_dev_stop(opt->dev_id);
rte_event_dev_close(opt->dev_id);
}
--
2.21.0
next prev parent reply other threads:[~2019-03-01 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 7:16 [dpdk-dev] [PATCH 1/3] examples/eventdev_pipeline: configure max events based on dev info Pavan Nikhilesh Bhagavatula
2019-03-01 7:16 ` [dpdk-dev] [PATCH 2/3] examples/eventdev_pipeline: follow proper teardown sequence Pavan Nikhilesh Bhagavatula
2019-03-11 9:57 ` Van Haaren, Harry
2019-03-01 7:16 ` Pavan Nikhilesh Bhagavatula [this message]
2019-03-11 9:58 ` [dpdk-dev] [PATCH 3/3] app/eventdev: " Van Haaren, Harry
2019-03-11 15:12 ` Jerin Jacob Kollanukkaran
2019-03-08 18:25 ` [dpdk-dev] [PATCH 1/3] examples/eventdev_pipeline: configure max events based on dev info Jerin Jacob Kollanukkaran
2019-03-11 9:57 ` Van Haaren, Harry
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=20190301071617.6570-3-pbhagavatula@marvell.com \
--to=pbhagavatula@marvell.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jerinj@marvell.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).