FIFO/Pipe Implementation

Gedare Bloom gedare at rtems.org
Sun Apr 15 18:17:14 UTC 2012


Can we use the posix condvar to solve this particular problem?

Should we pull the posix condvar implementation into the score so that
we can use a shared condition variable implementation in the classic
api?

On Sun, Apr 15, 2012 at 2:13 PM, Gedare Bloom <gedare at rtems.org> wrote:
> This sounds like a bug we should file a PR.
>
> On Thu, Apr 12, 2012 at 7:11 PM, Joel Sherrill
> <joel.sherrill at oarcorp.com> wrote:
>> FWIW the fifo/pipe code was a previous year's gsoc. It does not have full code coverage and I recall that Coverity had issues with it. I would not be surprised at issues.
>>
>> An efficient key-like object and condition variable in the Classic API would be great. Especially if the score is enhanced so the API versions are just wrappers or users of score capabilities.
>>
>> Chris Johns <chrisj at rtems.org> wrote:
>>
>>>On 12/04/12 10:30 PM, Sebastian Huber wrote:
>>>>
>>>> Please note that this approach is not SMP proof. I think we need
>>>> condition variables in the RTEMS Classic API.
>>>>
>>>
>>>I agree. It is needed. I also would like to see a classic API version of
>>>the POSIX keys as part of an attempt to remove the task variables API.
>>>
>>>Chris
>>>_______________________________________________
>>>rtems-devel mailing list
>>>rtems-devel at rtems.org
>>>http://www.rtems.org/mailman/listinfo/rtems-devel
>>
>> _______________________________________________
>> rtems-devel mailing list
>> rtems-devel at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-devel



More information about the devel mailing list