Re: RTEMS SMP Status Report v3

2017-01-09 Thread Chris Johns
On 24/12/16 7:56 am, Gedare Bloom wrote: > On Fri, Dec 23, 2016 at 4:45 AM, Sebastian Huber > wrote: >> On 23/12/16 02:01, Chris Johns wrote: >>> >>> I like the idea of ELF notes being used to tag every API function in RTEMS >>> with the standard and API they come from. We can then have a tool to

Re: RTEMS SMP Status Report v3

2016-12-23 Thread Gedare Bloom
On Fri, Dec 23, 2016 at 4:45 AM, Sebastian Huber wrote: > On 23/12/16 02:01, Chris Johns wrote: >> >> On 22/12/2016 21:43, Sebastian Huber wrote: >>> >>> - Chris Johns schrieb: On 22/12/2016 01:19, Sebastian Huber wrote: > > The POSIX API provides no binary semaphores, so ta

Re: RTEMS SMP Status Report v3

2016-12-23 Thread Sebastian Huber
On 23/12/16 02:01, Chris Johns wrote: On 22/12/2016 21:43, Sebastian Huber wrote: - Chris Johns schrieb: On 22/12/2016 01:19, Sebastian Huber wrote: The POSIX API provides no binary semaphores, so task/interrupt synchronization is a problem. So, for drivers there is still a need for som

Re: RTEMS SMP Status Report v3

2016-12-22 Thread Chris Johns
On 22/12/2016 21:43, Sebastian Huber wrote: - Chris Johns schrieb: On 22/12/2016 01:19, Sebastian Huber wrote: The POSIX API provides no binary semaphores, so task/interrupt synchronization is a problem. So, for drivers there is still a need for some RTEMS-specific APIs. I like the idea

Re: RTEMS SMP Status Report v3

2016-12-22 Thread Sebastian Huber
- Cudmore, Alan P. (GSFC-5820) schrieb: > Interesting. On our 40Mhz Coldfire CPU, one of our developers did note how > the RTEMS semaphore calls were slow. It would be quite interesting if you could run the tmtests with your version and the current Git master. The new tmfine01 tests some

Re: RTEMS SMP Status Report v3

2016-12-22 Thread Sebastian Huber
- Chris Johns schrieb: > On 22/12/2016 01:19, Sebastian Huber wrote: > > The POSIX API provides no binary semaphores, so task/interrupt > > synchronization is a problem. So, for drivers there is still a need for > > some RTEMS-specific APIs. > > I like the idea of NP additions help us here.

Re: RTEMS SMP Status Report v3

2016-12-21 Thread Chris Johns
On 22/12/2016 01:19, Sebastian Huber wrote: The POSIX API provides no binary semaphores, so task/interrupt synchronization is a problem. So, for drivers there is still a need for some RTEMS-specific APIs. I like the idea of NP additions help us here. We already have pthread_getaffinity_np. A

Re: RTEMS SMP Status Report v3

2016-12-21 Thread Cudmore, Alan P. (GSFC-5820)
Interesting. On our 40Mhz Coldfire CPU, one of our developers did note how the RTEMS semaphore calls were slow. So currently the self-contained objects are more efficient, but do not provide as many real-time features. Your changes to convert the POSIX objects to self-contained would help impr

Re: RTEMS SMP Status Report v3

2016-12-21 Thread Sebastian Huber
On 21/12/16 15:02, Cudmore, Alan P. (GSFC-5820) wrote: I agree, it’s an excellent report. Thanks for the SMP implementation in RTEMS, it is very important to our future work. In the past I have used the classic RTEMS API. For SMP applications, is there a preferred API? Does the POSIX API offer

Re: RTEMS SMP Status Report v3

2016-12-21 Thread Cudmore, Alan P. (GSFC-5820)
I agree, it’s an excellent report. Thanks for the SMP implementation in RTEMS, it is very important to our future work. In the past I have used the classic RTEMS API. For SMP applications, is there a preferred API? Does the POSIX API offer more control or features over the Classic API for SMP?

Re: RTEMS SMP Status Report v3

2016-12-20 Thread Sebastian Huber
On 20/12/16 23:43, Chris Johns wrote: On 21/12/2016 08:45, Gedare Bloom wrote: On Tue, Dec 20, 2016 at 4:12 PM, Chris Johns wrote: On 19/12/2016 20:07, Sebastian Huber wrote: Hello, there is a third version of an RTEMS SMP Status Report available at: http://microelectronics.esa.int/gr74

Re: RTEMS SMP Status Report v3

2016-12-20 Thread Chris Johns
On 21/12/2016 08:45, Gedare Bloom wrote: On Tue, Dec 20, 2016 at 4:12 PM, Chris Johns wrote: On 19/12/2016 20:07, Sebastian Huber wrote: Hello, there is a third version of an RTEMS SMP Status Report available at: http://microelectronics.esa.int/gr740/RTEMS-SMP-StatusReportEmbBrains-rev3-20

Re: RTEMS SMP Status Report v3

2016-12-20 Thread Gedare Bloom
On Tue, Dec 20, 2016 at 4:12 PM, Chris Johns wrote: > On 19/12/2016 20:07, Sebastian Huber wrote: >> >> Hello, >> >> there is a third version of an RTEMS SMP Status Report available at: >> >> >> http://microelectronics.esa.int/gr740/RTEMS-SMP-StatusReportEmbBrains-rev3-2016-12.pdf >> > > This is a

Re: RTEMS SMP Status Report v3

2016-12-20 Thread Chris Johns
On 19/12/2016 20:07, Sebastian Huber wrote: Hello, there is a third version of an RTEMS SMP Status Report available at: http://microelectronics.esa.int/gr740/RTEMS-SMP-StatusReportEmbBrains-rev3-2016-12.pdf This is an excellent report. Should some parts of this be added to the User Manual u

RTEMS SMP Status Report v3

2016-12-19 Thread Sebastian Huber
Hello, there is a third version of an RTEMS SMP Status Report available at: http://microelectronics.esa.int/gr740/RTEMS-SMP-StatusReportEmbBrains-rev3-2016-12.pdf -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax :