eal: fix spelling errors
PATCH 1/1 eal: fix spelling errors
Fix spelling errors in comments (found with codespell).
Note that "inbetween" is not correct in English and should either be two words or better yet, the in can be dropped.
https://www.grammarly.com/blog/in-between-or-inbetween/
--- lib/librte_eal/common/eal_common_fbarray.c | 2 +- lib/librte_eal/common/include/arch/arm/rte_atomic_64.h | 2 +- lib/librte_eal/common/include/arch/arm/rte_cycles_32.h | 2 +- lib/librte_eal/common/include/arch/x86/rte_atomic.h | 2 +- lib/librte_eal/common/malloc_elem.c | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-)
lib/librte_eal/common/eal_common_fbarray.c +1 -1
@@ -1337,7 +1337,7 @@ fbarray_find_biggest(struct rte_fbarray *arr, unsigned int start, bool used,*/ /* the API's called are thread-safe, but something may still happen -* inbetween the API calls, so lock the fbarray. all other API's are +* between the API calls, so lock the fbarray. all other API's are * read-locking the fbarray, so read lock here is OK. */ rte_rwlock_read_lock (&arr->rwlock);
lib/librte_eal/common/include/arch/arm/rte_atomic_64.h +1 -1
@@ -87,7 +87,7 @@ rte_atomic128_cmp_exchange(rte_int128_t *dst, rte_int128_t *exp, const rte_int128_t *src, unsigned int weak, int success, int failure) { -/* Always do strong CAS */ +/* Always do strong CASE */ RTE_SET_USED (weak );/* Ignore memory ordering for failure, memory order for * success must be stronger or equal
lib/librte_eal/common/include/arch/arm/rte_cycles_32.h +1 -1
@@ -57,7 +57,7 @@ __rte_rdtsc_syscall(void)* asm volatile("mcr p15, 0, %0, c9, c12, 0" : : "r"(29)); * asm volatile("mcr p15, 0, %0, c9, c12, 1" : : "r"(0x8000000f)); * -* which is possible only from the priviledged mode (kernel space). +* which is possible only from the privileged mode (kernel space). */ static inline uint64_t __rte_rdtsc_pmccntr (void )
lib/librte_eal/common/include/arch/x86/rte_atomic.h +1 -1
@@ -55,7 +55,7 @@ extern "C" {* * As pointed by Java guys, that makes possible to use lock-prefixed * instructions to get the same effect as mfence and on most modern HW -* that gives a better perfomance then using mfence: +* that gives a better performance then using mfence: * https://shipilev.net/blog/2014/on-the-fence-with-dependencies/ * Basic idea is to use lock prefixed add with some dummy memory location * as the destination. From their experiments 128B(2 cache lines) below
lib/librte_eal/common/malloc_elem.c +1 -1
@@ -171,7 +171,7 @@ malloc_elem_insert(struct malloc_elem *elem) next_elem =NULL ; heap->last = elem; }else { -/* the new memory is somewhere inbetween start and end */ +/* the new memory is somewhere between start and end */ uint64_t dist_from_start, dist_from_end; dist_from_end =RTE_PTR_DIFF (heap->last, elem);
Signature · 1 line
2.20.1
PATCH v2 1/1 eal: fix spelling errors
Fix spelling errors in comments (found with codespell).
Note that "inbetween" is not correct in English and should either be two words or better yet, the in can be dropped.
https://www.grammarly.com/blog/in-between-or-inbetween/
---
v2 - drop mistaken fix to arm/rte_atomic_64.h
lib/librte_eal/common/eal_common_fbarray.c | 2 +- lib/librte_eal/common/include/arch/arm/rte_cycles_32.h | 2 +- lib/librte_eal/common/include/arch/x86/rte_atomic.h | 2 +- lib/librte_eal/common/malloc_elem.c | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-)
lib/librte_eal/common/eal_common_fbarray.c +1 -1
@@ -1337,7 +1337,7 @@ fbarray_find_biggest(struct rte_fbarray *arr, unsigned int start, bool used,*/ /* the API's called are thread-safe, but something may still happen -* inbetween the API calls, so lock the fbarray. all other API's are +* between the API calls, so lock the fbarray. all other API's are * read-locking the fbarray, so read lock here is OK. */ rte_rwlock_read_lock (&arr->rwlock);
lib/librte_eal/common/include/arch/arm/rte_cycles_32.h +1 -1
@@ -57,7 +57,7 @@ __rte_rdtsc_syscall(void)* asm volatile("mcr p15, 0, %0, c9, c12, 0" : : "r"(29)); * asm volatile("mcr p15, 0, %0, c9, c12, 1" : : "r"(0x8000000f)); * -* which is possible only from the priviledged mode (kernel space). +* which is possible only from the privileged mode (kernel space). */ static inline uint64_t __rte_rdtsc_pmccntr (void )
lib/librte_eal/common/include/arch/x86/rte_atomic.h +1 -1
@@ -55,7 +55,7 @@ extern "C" {* * As pointed by Java guys, that makes possible to use lock-prefixed * instructions to get the same effect as mfence and on most modern HW -* that gives a better perfomance then using mfence: +* that gives a better performance then using mfence: * https://shipilev.net/blog/2014/on-the-fence-with-dependencies/ * Basic idea is to use lock prefixed add with some dummy memory location * as the destination. From their experiments 128B(2 cache lines) below
lib/librte_eal/common/malloc_elem.c +1 -1
@@ -171,7 +171,7 @@ malloc_elem_insert(struct malloc_elem *elem) next_elem =NULL ; heap->last = elem; }else { -/* the new memory is somewhere inbetween start and end */ +/* the new memory is somewhere between start and end */ uint64_t dist_from_start, dist_from_end; dist_from_end =RTE_PTR_DIFF (heap->last, elem);
Signature · 1 line
2.20.1
Thomas Monjalon
Applied10/03/2020 17:35, Stephen Hemminger:
Quoted 7 lines
Fix spelling errors in comments (found with codespell).
Note that "inbetween" is not correct in English and should either be two words or better yet, the in can be dropped.
https://www.grammarly.com/blog/in-between-or-inbetween/Signed-off-by Stephen Hemminger <[email protected]>
Applied, thanks