source: rtems-docs/posix-users/status_of_implementation.rst @ 42d50d7

5
Last change on this file since 42d50d7 was 6543b90, checked in by Gedare Bloom <gedare@…>, on 07/26/17 at 15:50:10

posix1003-1, posix_users: mark mmap and shm functions implemented

Update #2859.

  • Property mode set to 100644
File size: 1.5 KB
Line 
1.. comment SPDX-License-Identifier: CC-BY-SA-4.0
2
3Status of Implementation
4########################
5
6This chapter provides an overview of the status of the implementation
7of the POSIX API for RTEMS.  The *POSIX 1003.1b Compliance Guide*
8provides more detailed information regarding the implementation of
9each of the numerous functions, constants, and macros specified by
10the POSIX 1003.1b standard.
11
12RTEMS supports many of the process and user/group oriented services
13in a "single user/single process" manner.  This means that although
14these services may be of limited usefulness or functionality, they
15are provided and do work in a coherent manner.  This is significant
16when porting existing code from UNIX to RTEMS.
17
18- Implementation
19
20  - The current implementation of ``dup()`` is insufficient.
21  - FIFOs ``mkfifo()`` are not currently implemented.
22  - Asynchronous IO is not implemented.
23  - The ``flockfile()`` family is not implemented
24  - getc/putc unlocked family is not implemented
25  - Mapped Memory is partially implemented
26  - NOTES:
27
28    - For Shared Memory and Mapped Memory services, it is unclear what
29      level of support is appropriate and possible for RTEMS.
30
31- Functional Testing
32
33  - Tests for unimplemented services
34
35- Performance Testing
36
37  - There are no POSIX Performance Tests.
38
39- Documentation
40
41  - Many of the service description pages are not complete in this
42    manual.  These need to be completed and information added to the
43    background and operations sections.
44
45  - Example programs (not just tests) would be very nice.
Note: See TracBrowser for help on using the repository browser.