View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001996 | 1003.1(2024)/Issue8 | System Interfaces | public | 2026-08-16 16:53 | 2026-08-16 16:53 |
| Reporter | dhruv | Assigned To | |||
| Priority | normal | Severity | Editorial | Type | Enhancement Request |
| Status | New | Resolution | Open | ||
| Name | Dhruv McElwaine | ||||
| Organization | Independent | ||||
| User Reference | |||||
| Section | 2.3.2 Realtime Signal Generation and Delivery | ||||
| Page Number | N/A | ||||
| Line Number | N/A | ||||
| Interp Status | |||||
| Final Accepted Text | |||||
| Summary | 0001996: Add SIGEV_SIGNAL_THREAD to allow more efficient handling of sigevent-using functions. | ||||
| Description | Currently, there are only two notification mechanisms for use with sigevent: SIGEV_SIGNAL and SIGEV_THREAD. Both of these methods have issue preventing their use, and so a new notification should be added. SIGEV_THREAD typically spawns a new thread on each event, which degrades performance to the point that it defeats the purpose of using such a notification; performing the corresponding blocking opperation in a new thread would typically be both faster and more convenient. SIGEV_SIGNAL requires use of a signal handler; as signal handlers are shared between all threads in a process, this makes it unsuitable for use in a library. To resolve this, several platforms have added mechanisms to direct the signal to a specific thread. However, this mechanism is not standardised, which imhibits its use. This proposal serves to standardise it. | ||||
| Desired Action | In 2.3.2 Realtime Signal Generation and Delivery: Append to the definition of the sigevent struct an additional field called sigev_notify_thread of type pthread_t. Add an addition entry to the list of valid values for sigev_notify: SIGEV_SIGNAL_THREAD:
| ||||
| Tags | enhancement | ||||
