From: Richard Palethorpe <rpalethorpe@suse.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 5/7] fzsync: Move yield check out of loop and add yield to delay
Date: Tue, 13 Apr 2021 08:07:51 +0100 [thread overview]
Message-ID: <20210413070753.1691-6-rpalethorpe@suse.com> (raw)
In-Reply-To: <20210413070753.1691-1-rpalethorpe@suse.com>
During my testing I found no difference between having the branch
inside the loop and outside. However looking at the generated
assembly, it definitely does perform the branch inside the loop. This
could have an effect on some platform with worse branch prediction. So
I have moved the branch outside of the loop.
Also I have added sched_yield to the delay loop. If we only have one
CPU then it is not delaying anything unless the other process can
progress.
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
Acked-by: Petr Vorel <pvorel@suse.cz>
Reviewed-by: Li Wang <liwang@redhat.com>
---
include/tst_fuzzy_sync.h | 72 ++++++++++++++++++++++++++++++----------
1 file changed, 54 insertions(+), 18 deletions(-)
diff --git a/include/tst_fuzzy_sync.h b/include/tst_fuzzy_sync.h
index 5474f81e3..36a604e13 100644
--- a/include/tst_fuzzy_sync.h
+++ b/include/tst_fuzzy_sync.h
@@ -183,9 +183,9 @@ struct tst_fzsync_pair {
int exec_loop;
/** Internal; The second thread or 0 */
pthread_t thread_b;
- /**
- * Internal; The flag indicates single core machines or not
- *
+ /**
+ * The flag indicates single core machines or not
+ *
* If running on single core machines, it would take considerable
* amount of time to run fuzzy sync library.
* Thus call sched_yield to give up cpu to decrease the test time.
@@ -575,31 +575,53 @@ static inline void tst_fzsync_pair_wait(int *our_cntr,
* line above before doing that. If we are in rear position
* then our counter may already have been set to zero.
*/
- while (tst_atomic_load(our_cntr) > 0
- && tst_atomic_load(our_cntr) < INT_MAX) {
- if (spins)
- (*spins)++;
- if(yield_in_wait)
+ if (yield_in_wait) {
+ while (tst_atomic_load(our_cntr) > 0
+ && tst_atomic_load(our_cntr) < INT_MAX) {
+ if (spins)
+ (*spins)++;
+
sched_yield();
+ }
+ } else {
+ while (tst_atomic_load(our_cntr) > 0
+ && tst_atomic_load(our_cntr) < INT_MAX) {
+ if (spins)
+ (*spins)++;
+ }
}
+
tst_atomic_store(0, other_cntr);
/*
* Once both counters have been set to zero the invariant
* is restored and we can continue.
*/
- while (tst_atomic_load(our_cntr) > 1)
- ;
+ if (yield_in_wait) {
+ while (tst_atomic_load(our_cntr) > 1)
+ sched_yield();
+ } else {
+ while (tst_atomic_load(our_cntr) > 1)
+ ;
+ }
} else {
/*
* If our counter is less than the other thread's we are ahead
* of it and need to wait.
*/
- while (tst_atomic_load(our_cntr) < tst_atomic_load(other_cntr)) {
- if (spins)
- (*spins)++;
- if(yield_in_wait)
+ if (yield_in_wait) {
+ while (tst_atomic_load(our_cntr) <
+ tst_atomic_load(other_cntr)) {
+ if (spins)
+ (*spins)++;
sched_yield();
+ }
+ } else {
+ while (tst_atomic_load(our_cntr) <
+ tst_atomic_load(other_cntr)) {
+ if (spins)
+ (*spins)++;
+ }
}
}
}
@@ -713,8 +735,15 @@ static inline void tst_fzsync_start_race_a(struct tst_fzsync_pair *pair)
tst_fzsync_wait_a(pair);
delay = pair->delay;
- while (delay < 0)
- delay++;
+ if (pair->yield_in_wait) {
+ while (delay < 0) {
+ sched_yield();
+ delay++;
+ }
+ } else {
+ while (delay < 0)
+ delay++;
+ }
tst_fzsync_time(&pair->a_start);
}
@@ -744,8 +773,15 @@ static inline void tst_fzsync_start_race_b(struct tst_fzsync_pair *pair)
tst_fzsync_wait_b(pair);
delay = pair->delay;
- while (delay > 0)
- delay--;
+ if (pair->yield_in_wait) {
+ while (delay > 0) {
+ sched_yield();
+ delay--;
+ }
+ } else {
+ while (delay > 0)
+ delay--;
+ }
tst_fzsync_time(&pair->b_start);
}
--
2.30.2
next prev parent reply other threads:[~2021-04-13 7:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 7:07 [LTP] [PATCH v4 0/7] Fuzzy Sync single core support and tests Richard Palethorpe
2021-04-13 7:07 ` [LTP] [PATCH v4 1/7] fzsync: Add self tests Richard Palethorpe
2021-04-13 8:34 ` Cyril Hrubis
2021-04-13 7:07 ` [LTP] [PATCH v4 2/7] fzsync: Reset delay bias Richard Palethorpe
2021-04-13 7:07 ` [LTP] [PATCH v4 3/7] fzsync: Correctly print positive lower delay range bound Richard Palethorpe
2021-04-13 7:07 ` [LTP] [PATCH v4 4/7] fzsync: Add sched_yield for single core machine Richard Palethorpe
2021-04-13 7:07 ` Richard Palethorpe [this message]
2021-04-13 7:07 ` [LTP] [PATCH v4 6/7] API: Add tst_ncpus_available Richard Palethorpe
2021-04-13 7:07 ` [LTP] [PATCH v4 7/7] fzsync: Check processor affinity Richard Palethorpe
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=20210413070753.1691-6-rpalethorpe@suse.com \
--to=rpalethorpe@suse.com \
--cc=ltp@lists.linux.it \
/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