From: Rebecca Troy <rebecca.troy@intel.com>
To: dev@dpdk.org
Cc: ciara.power@intel.com, Rebecca Troy <rebecca.troy@intel.com>,
Declan Doherty <declan.doherty@intel.com>
Subject: [dpdk-dev] [PATCH] test/crypto: rename slave to worker
Date: Wed, 30 Jun 2021 15:29:39 +0000 [thread overview]
Message-ID: <20210630152939.463904-1-rebecca.troy@intel.com> (raw)
Modifies the scheduler tests in the crypto unit test suite
to replace the usage of the word 'slave' with the more
appropriate word 'worker'.
The scheduler test functions were modified as follows:
test_scheduler_attach_slave_op is now called
test_scheduler_attach_worker_op,
test_scheduler_detach_slave_op is
test_scheduler_detach_worker_op.
Signed-off-by: Rebecca Troy <rebecca.troy@intel.com>
---
app/test/test_cryptodev.c | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
index 39db52b17a..1725d6154c 100644
--- a/app/test/test_cryptodev.c
+++ b/app/test/test_cryptodev.c
@@ -13474,7 +13474,7 @@ scheduler_testsuite_setup(void)
}
static int
-test_scheduler_attach_slave_op(void)
+test_scheduler_attach_worker_op(void)
{
struct crypto_testsuite_params *ts_params = &testsuite_params;
uint8_t sched_id = ts_params->valid_devs[0];
@@ -13584,7 +13584,7 @@ test_scheduler_attach_slave_op(void)
}
static int
-test_scheduler_detach_slave_op(void)
+test_scheduler_detach_worker_op(void)
{
struct crypto_testsuite_params *ts_params = &testsuite_params;
uint8_t sched_id = ts_params->valid_devs[0];
@@ -13650,7 +13650,7 @@ test_scheduler_mode_pkt_size_distr_op(void)
static int
scheduler_multicore_testsuite_setup(void)
{
- if (test_scheduler_attach_slave_op() < 0)
+ if (test_scheduler_attach_worker_op() < 0)
return TEST_SKIPPED;
if (test_scheduler_mode_op(CDEV_SCHED_MODE_MULTICORE) < 0)
return TEST_SKIPPED;
@@ -13660,7 +13660,7 @@ scheduler_multicore_testsuite_setup(void)
static int
scheduler_roundrobin_testsuite_setup(void)
{
- if (test_scheduler_attach_slave_op() < 0)
+ if (test_scheduler_attach_worker_op() < 0)
return TEST_SKIPPED;
if (test_scheduler_mode_op(CDEV_SCHED_MODE_ROUNDROBIN) < 0)
return TEST_SKIPPED;
@@ -13670,7 +13670,7 @@ scheduler_roundrobin_testsuite_setup(void)
static int
scheduler_failover_testsuite_setup(void)
{
- if (test_scheduler_attach_slave_op() < 0)
+ if (test_scheduler_attach_worker_op() < 0)
return TEST_SKIPPED;
if (test_scheduler_mode_op(CDEV_SCHED_MODE_FAILOVER) < 0)
return TEST_SKIPPED;
@@ -13680,7 +13680,7 @@ scheduler_failover_testsuite_setup(void)
static int
scheduler_pkt_size_distr_testsuite_setup(void)
{
- if (test_scheduler_attach_slave_op() < 0)
+ if (test_scheduler_attach_worker_op() < 0)
return TEST_SKIPPED;
if (test_scheduler_mode_op(CDEV_SCHED_MODE_PKT_SIZE_DISTR) < 0)
return TEST_SKIPPED;
@@ -13690,7 +13690,7 @@ scheduler_pkt_size_distr_testsuite_setup(void)
static void
scheduler_mode_testsuite_teardown(void)
{
- test_scheduler_detach_slave_op();
+ test_scheduler_detach_worker_op();
}
#endif /* RTE_CRYPTO_SCHEDULER */
@@ -14652,12 +14652,12 @@ test_cryptodev_scheduler(void /*argv __rte_unused, int argc __rte_unused*/)
static struct unit_test_suite scheduler_config = {
.suite_name = "Crypto Device Scheduler Config Unit Test Suite",
.unit_test_cases = {
- TEST_CASE(test_scheduler_attach_slave_op),
+ TEST_CASE(test_scheduler_attach_worker_op),
TEST_CASE(test_scheduler_mode_multicore_op),
TEST_CASE(test_scheduler_mode_roundrobin_op),
TEST_CASE(test_scheduler_mode_failover_op),
TEST_CASE(test_scheduler_mode_pkt_size_distr_op),
- TEST_CASE(test_scheduler_detach_slave_op),
+ TEST_CASE(test_scheduler_detach_worker_op),
TEST_CASES_END() /**< NULL terminate array */
}
--
2.25.1
next reply other threads:[~2021-06-30 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 15:29 Rebecca Troy [this message]
2021-07-07 14:23 ` [dpdk-dev] [EXT] " 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=20210630152939.463904-1-rebecca.troy@intel.com \
--to=rebecca.troy@intel.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@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).