"6348ace8" (history) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:"6348 ace8" (Results 1 – 5 of 5) sorted by relevance

/freebsd/lib/librt/
H A D	sigev_thread.h	6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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	6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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	6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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	6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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	aio.c	6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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. 6348ace8 Sat Mar 04 00:18:19 GMT 2006 David Xu <davidxu@FreeBSD.org> 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.