Any comments on the tests?
2016-06-21 14:36 GMT-07:00 Charles Cui :
> Hi Christos,
>
> Some updates on the tests of priority protect.
> You need to apply my new patch here,
> https://github.com/ycui1984/posixtestsuite/blob/master/patches/PRIOPROTECT_AND_GETCLOCK/0005-extend-sched_param.patch
>
Thanks Christos for these comments!
In terms of the new fields exposed by sched_param, those are only for
testing convenience, if we decide to expose those to users, we need to
consider carefully.
In terms of the testing method proposed by you, did you already implement
and test
or want me to prov
On Jun 22, 3:11pm, charles.cui1...@gmail.com (Charles Cui) wrote:
-- Subject: Re: _SC_SIGQUEUE_MAX
| Thanks Christos for these comments!
| In terms of the new fields exposed by sched_param, those are only for
| testing convenience, if we decide to expose those to users, we need to
| consider care
On Jun 22, 1:23pm, charles.cui1...@gmail.com (Charles Cui) wrote:
-- Subject: Re: _SC_SIGQUEUE_MAX
| Any comments on the tests?
Yes, I am not finished yet testing and looking. Here are some preliminary
ones:
1. You've added more fields to sched_params. This should not be done lightly
because
I have write a draft of the benchmark, but have not verified successfully
on the patched system.
The idea is to
1. create a mutexattr data structure and set pthread priority protect
protocol.
2. set the real time scheduling policy.
3. use the mutexattr to init a mutex.
4. create 2 threads to conten
