On Wed, Jul 06, 2011 at 02:19:47PM +0200, Gilles Chanteperdrix wrote:
On 07/06/2011 01:42 PM, Andrey Nechypurenko wrote:
What makes me worry here is the IPC abbreviation - I have just one
process with multiple threads. So would not real IPC mechanism be the
overkill in this scenario? Or
On 07/07/2011 09:31 AM, Richard Cochran wrote:
On Wed, Jul 06, 2011 at 02:19:47PM +0200, Gilles Chanteperdrix wrote:
On 07/06/2011 01:42 PM, Andrey Nechypurenko wrote:
What makes me worry here is the IPC abbreviation - I have just one
process with multiple threads. So would not real IPC
Thank you very much guys for suggestions!
The idea with simple ring buffer looks promising and I will try to
implement it this way.
Once again thank you!
Andrey.
___
Xenomai-help mailing list
Xenomai-help@gna.org
Hi Folks,
In my application I have Xenomai thread which collects and process
sensor data. In addition, I have non-RT thread which sends sensor data
over the network for visualization (with much lower time resolution,
picking let's say every 100th sample). Xenomai thread is the only one
which
On 07/06/2011 11:25 AM, Andrey Nechypurenko wrote:
Hi Folks,
In my application I have Xenomai thread which collects and process
sensor data. In addition, I have non-RT thread which sends sensor data
over the network for visualization (with much lower time resolution,
picking let's say every
Thanks Gilles for the quick response!
You can use mutexes with priority inheritance to avoid this issue. But
Xenomai has ready made queues for rt/non-rt communication, the rtipcs:
http://www.xenomai.org/documentation/xenomai-head/html/api/group__rtipc.html
What makes me worry here is the IPC
On 07/06/2011 01:42 PM, Andrey Nechypurenko wrote:
Thanks Gilles for the quick response!
You can use mutexes with priority inheritance to avoid this issue. But
Xenomai has ready made queues for rt/non-rt communication, the rtipcs:
