From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/2] Updates to pthread_{barrier,cond}_destroy()
Date: Thu, 12 Oct 2017 15:14:45 +0200 [thread overview]
Message-ID: <20171012131445.GA21253@rei> (raw)
In-Reply-To: <20171009101824.17251-1-rpalethorpe@suse.com>
Hi!
> These tests do naturally include race conditions and waste time in calls to
> sleep, we could mitigate them by using another synchronisation mechanism (e.g
> TST_CHECKPOINT or fzsync), but not remove them completely. I'm not sure whether
> introducing LTP library functions into the POSIX tests is a good idea or not.
We try to avoid any Linux specific code in the Open Posix Testsuite and
generally try to stick only to POSIX APIs there. This is not always
possible though, so we have some code in include/ that is not portable
and has to be reimplemented per each Unix platform, for instance the
affinity.h. But we try to avoid that as much as we can, hence we do not
make use any of the LTP test library here, since quite a lot of the code
we have in there is Linux specific.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2017-10-12 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 10:18 [LTP] [PATCH 0/2] Updates to pthread_{barrier,cond}_destroy() Richard Palethorpe
2017-10-09 10:18 ` [LTP] [PATCH 1/2] POSIX: Allow pthread_barrier_destroy() to block Richard Palethorpe
2017-10-12 13:34 ` Cyril Hrubis
2017-10-13 8:58 ` Richard Palethorpe
2017-10-13 9:37 ` Cyril Hrubis
2017-10-13 12:57 ` Richard Palethorpe
2017-10-09 10:18 ` [LTP] [PATCH 2/2] POSIX: Allow pthread_cond_destroy " Richard Palethorpe
2017-10-12 14:01 ` Cyril Hrubis
2017-10-13 9:06 ` Richard Palethorpe
2017-10-13 9:20 ` Cyril Hrubis
2017-10-12 13:14 ` Cyril Hrubis [this message]
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=20171012131445.GA21253@rei \
--to=chrubis@suse.cz \
--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