[POSIX Benchmark Test] psxtmmqrcvblock01 made (GCI 2018)

[Joel Sherrill]

I agree we want to reduce the overall number of executables but the timing
tests which block
need a large set of tasks which do precisely the right thing. You have to
be very careful not to
accidentally measure the overhead of _Thread_Handler or any odd
initialization.

I am happy to see the cases which don't block or unblock merged into single
cases. The
newly added pthread attr tmtest has a lot of cases. But blocking,
unblocking, and preemption
cases need to be separate. They are very precise tests and hard to make
sure they measure
exactly what you think they measure without extras.

--joel

On Fri, Nov 16, 2018 at 7:30 AM Shashvat Jain <shashvatjain2002 at gmail.com>
wrote:

> I asked that before starting to make the test and Dr. Joel asked me to
> make a separate one
>
>
>
> On Fri, Nov 16, 2018 at 12:35 PM Sebastian Huber <
> sebastian.huber at embedded-brains.de> wrote:
>
>> Do we really need separate test programs for all these test cases? Can't
>> we just add this to psxtmmq01?
>>
>> The reason for this is that it needs time to load a test program to the
>> target.
>>
>> --
>> Sebastian Huber, embedded brains GmbH
>>
>> Address : Dornierstr. 4, D-82178 Puchheim, Germany
>> Phone   : +49 89 189 47 41-16
>> Fax     : +49 89 189 47 41-09
>> E-Mail  : sebastian.huber at embedded-brains.de
>> PGP     : Public key available on request.
>>
>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>>
>> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20181116/28f1226b/attachment-0002.html>