Philippe Gerum wrote:
> On Mon, 2010-08-02 at 08:01 +0200, Gilles Chanteperdrix wrote:
>> Due to their limitations on ARM platform (they are uncached on pre-v6
>> ARMs), RT_HEAP should more be reserved to communications between
>> user-space tasks and kernel-space tasks on these platforms. For
>> communications between two user-space processes, using plain Linux
>> shared memories is recommended.
>>
>
> ARM VIVT caching kills common sense. Note that in the particular case of
> a rt / non-rt communication, standard shm would imply priority inversion
> induced by heavyweight synchronization between rt senders and non-rt
> receivers, so that would not fly that well. This is still possible to
> use a lockless approach to queue data though. YMMV.
Well, in fact, with the native API, you have the choice to use cached or
non-cached heaps. So, if you know the heap will be used only by
user-space applications, you can keep the heap cached, and forgot what I
said. And Bob uses an OMAP3 anyway if I am not mistaken, so he has a
shiny VIPT cache.
--
Gilles.
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
