remove repeated 'the' in the code

[dpdk.git] / app / test / test_barrier.c

diff --git a/app/test/test_barrier.c b/app/test/test_barrier.c
index 43b5f62..6d6d487 100644 (file)
--- a/app/test/test_barrier.c
+++ b/app/test/test_barrier.c
@@ -6,7 +6,7 @@
   * This is a simple functional test for rte_smp_mb() implementation.
   * I.E. make sure that LOAD and STORE operations that precede the
   * rte_smp_mb() call are globally visible across the lcores
-  * before the the LOAD and STORE operations that follows it.
+  * before the LOAD and STORE operations that follows it.
   * The test uses simple implementation of Peterson's lock algorithm
   * (https://en.wikipedia.org/wiki/Peterson%27s_algorithm)
   * for two execution units to make sure that rte_smp_mb() prevents
@@ -24,7 +24,6 @@
 #include <rte_memory.h>
 #include <rte_per_lcore.h>
 #include <rte_launch.h>
-#include <rte_atomic.h>
 #include <rte_eal.h>
 #include <rte_lcore.h>
 #include <rte_pause.h>
@@ -66,7 +65,7 @@ struct plock_test {
 struct lcore_plock_test {
        struct plock_test *pt[2]; /* shared, lock-protected data */
        uint64_t sum[2];          /* local copy of the shared data */
-       uint64_t iter;            /* number of iterations to perfom */
+       uint64_t iter;            /* number of iterations to perform */
        uint32_t lc;              /* given lcore id */
 };
 
@@ -236,7 +235,7 @@ plock_test(uint64_t iter, enum plock_use_type utype)
 
        /* test phase - start and wait for completion on each active lcore */
 
-       rte_eal_mp_remote_launch(plock_test1_lcore, lpt, CALL_MASTER);
+       rte_eal_mp_remote_launch(plock_test1_lcore, lpt, CALL_MAIN);
        rte_eal_mp_wait_lcore();
 
        /* validation phase - make sure that shared and local data match */