From: Richard Palethorpe <rpalethorpe@suse.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 0/7] Fuzzy Sync single core support and tests
Date: Tue, 13 Apr 2021 08:07:46 +0100 [thread overview]
Message-ID: <20210413070753.1691-1-rpalethorpe@suse.com> (raw)
Hello,
V4: (no change in logic)
* Remove useless variable in pair_init
* Explain TIME_SCALE
* Differentiate between "cs" variables when printing
* Add reviewed by trailers
V3:
* Add -pthread to test CFLAGS
* Substitute CPU_COUNT for CPU_COUNT_S and check for alloc failure
V2:
* Add tst_ncpus_available() to API
* Don't use CHK macro for yield_in_wait to prevent compiler warnings
* Simplify and split the test in two
I'm reasonably confident of the first tests correctness. The second is
maybe not complete and more formal analyses is needed IMO. I suspect
also that we can remove add_delay_bias and implement randomised
probing instead. The more I think about it the more clear it becomes,
but it may require some bigger changes to how we calculate and
introduce the delays.
Occasionally some tests may not reach the lower threshold and fail. It
may be caused by changes in the environment between the measuring and
delay implementation phases. This is also something which could be
investigated.
Anyway this is all still very time consuming and making it perform
well on single core is most important right now.
Leo Yu-Chi Liang (1):
fzsync: Add sched_yield for single core machine
Richard Palethorpe (6):
fzsync: Add self tests
fzsync: Reset delay bias
fzsync: Correctly print positive lower delay range bound
fzsync: Move yield check out of loop and add yield to delay
API: Add tst_ncpus_available
fzsync: Check processor affinity
include/tst_cpu.h | 1 +
include/tst_fuzzy_sync.h | 104 +++++++++---
lib/newlib_tests/.gitignore | 2 +
lib/newlib_tests/Makefile | 2 +
lib/newlib_tests/test16.c | 2 +
lib/newlib_tests/tst_fuzzy_sync01.c | 235 ++++++++++++++++++++++++++++
lib/newlib_tests/tst_fuzzy_sync02.c | 177 +++++++++++++++++++++
lib/tst_cpu.c | 26 +++
8 files changed, 525 insertions(+), 24 deletions(-)
create mode 100644 lib/newlib_tests/tst_fuzzy_sync01.c
create mode 100644 lib/newlib_tests/tst_fuzzy_sync02.c
--
2.30.2
next 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 Richard Palethorpe [this message]
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 ` [LTP] [PATCH v4 5/7] fzsync: Move yield check out of loop and add yield to delay Richard Palethorpe
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-1-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