From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 3/7] fzsync: Add long running thread support and deviation stats
Date: Fri, 29 Sep 2017 11:44:43 +0200 [thread overview]
Message-ID: <87efqpx2ic.fsf@our.domain.is.not.set> (raw)
In-Reply-To: <20170925160441.GC31931@rei>
Hello,
Cyril Hrubis writes:
> Hi!
>> This does not replace the delay method of synchronisation which can be used in
>> addition to the new method. Also the precision of the averages has been
>> reduced because double precision appears to be unnecessary.
>
> Just a quick question, have you tested this on arm as well? The x86 FPU
> computes with greater than float precission internally and I've seen a
> cases where code would run perfectly fine on x86 with floats but failed
> horrinbly on arm.
Ah, that is interesting. However I tested it again on ARM and the
figures appear to be the same. I think the average is fairly safe from
accumulative rounding errors.
--
Thank you,
Richard.
next prev parent reply other threads:[~2017-09-29 9:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 9:51 [LTP] [PATCH v4 1/7] tst_atomic: Add load, store and use __atomic builtins Richard Palethorpe
2017-09-25 9:51 ` [LTP] [PATCH v4 2/7] tst_atomic: Add atomic store and load tests Richard Palethorpe
2017-09-25 9:51 ` [LTP] [PATCH v4 3/7] fzsync: Add long running thread support and deviation stats Richard Palethorpe
2017-09-25 16:04 ` Cyril Hrubis
2017-09-29 9:44 ` Richard Palethorpe [this message]
2017-09-25 9:51 ` [LTP] [PATCH v4 4/7] fzsync: Add functionality test for library Richard Palethorpe
2017-09-25 9:51 ` [LTP] [PATCH v4 5/7] Convert cve-2016-7117 test to use long running threads Richard Palethorpe
2017-09-25 9:51 ` [LTP] [PATCH v4 6/7] Convert cve-2014-0196 " Richard Palethorpe
2017-09-26 10:05 ` Cyril Hrubis
2017-09-25 9:51 ` [LTP] [PATCH v4 7/7] Convert cve-2017-2671 " 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=87efqpx2ic.fsf@our.domain.is.not.set \
--to=rpalethorpe@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.