Searched hist:156267 (Results 1 - 5 of 5) sorted by relevance
| /freebsd-10.1-release/lib/librt/ | ||
| H A D | aio.c | diff 156267 Fri Mar 03 22:18:19 MST 2006 davidxu Use a thread pool to process notification if sigev_notify_attributes is default and caller does not require dedicated thread. timer needs a dedicated thread to maintain overrun count correctly in notification context. mqueue and aio can use thread pool to do notification concurrently, the thread pool has lifecycle control, some threads will exit if they have idled for a while. |
| H A D | sigev_thread.h | diff 156267 Fri Mar 03 22:18:19 MST 2006 davidxu Use a thread pool to process notification if sigev_notify_attributes is default and caller does not require dedicated thread. timer needs a dedicated thread to maintain overrun count correctly in notification context. mqueue and aio can use thread pool to do notification concurrently, the thread pool has lifecycle control, some threads will exit if they have idled for a while. |
| H A D | timer.c | diff 156267 Fri Mar 03 22:18:19 MST 2006 davidxu Use a thread pool to process notification if sigev_notify_attributes is default and caller does not require dedicated thread. timer needs a dedicated thread to maintain overrun count correctly in notification context. mqueue and aio can use thread pool to do notification concurrently, the thread pool has lifecycle control, some threads will exit if they have idled for a while. |
| H A D | mq.c | diff 156267 Fri Mar 03 22:18:19 MST 2006 davidxu Use a thread pool to process notification if sigev_notify_attributes is default and caller does not require dedicated thread. timer needs a dedicated thread to maintain overrun count correctly in notification context. mqueue and aio can use thread pool to do notification concurrently, the thread pool has lifecycle control, some threads will exit if they have idled for a while. |
| H A D | sigev_thread.c | diff 156267 Fri Mar 03 22:18:19 MST 2006 davidxu Use a thread pool to process notification if sigev_notify_attributes is default and caller does not require dedicated thread. timer needs a dedicated thread to maintain overrun count correctly in notification context. mqueue and aio can use thread pool to do notification concurrently, the thread pool has lifecycle control, some threads will exit if they have idled for a while. |
Completed in 161 milliseconds