vxWorks OSAL implementation should use static initialization where possible

[skliper]

OSAL has a concept of tables of resources, where the user can configure some maximum amount of those resources.

For example, the binary semaphore table could contain the static bytes of memory for the semaphore itself (using VX_BINARY_SEMAPHORE or an array of size VX_SEMAPHORE_SIZE taking care to maintain proper alignment) and then use semBInitialize on that memory when the OSAL wants to create a binary semaphore instead of allocating one from the resource pool. The user configures the maximum number of resources of each type, so it's ok to use the memory.

This enhancement would increase determinism in the system while maintaining the current API.

[skliper]

Imported from trac issue 149. Created by sseeger on 2016-01-10T01:08:42, last modified: 2019-08-14T14:11:46

[skliper]

Trac comment by jphickey on 2019-03-26 08:42:29:

Just saw this ticket. I totally agree and in fact vxworks-ng (not yet merged, ticket #231) is implemented using static memory for the semaphores just as described.

[skliper]

Confirmed current implementation uses tables. Closing this issue as no longer applicable (invalid).