History log of /freebsd/lib/librt/sigev_thread.c (Results 26 – 36 of 36)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 9199c09a 06-Jan-2010 Warner Losh <imp@FreeBSD.org>

Merge from head at r201628.

# This hasn't been tested, and there are at least three bad commits
# that need to be backed out before the branch will be stable again.


Revision tags: release/8.0.0_cvs, release/8.0.0
# 50f5f99b 18-Nov-2009 David Xu <davidxu@FreeBSD.org>

Fix compiler warnings.


Revision tags: release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0
# 650fff26 15-Aug-2008 Kip Macy <kmacy@FreeBSD.org>

atomic_fetchadd_int works on unsigned quantities - change
sigev_generation to be unsigned

MFC after: 1 month


Revision tags: release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0
# d688b9ce 29-Mar-2006 Daniel Eischen <deischen@FreeBSD.org>

Account for recent changes in namespace.h. Use _pthread_create
instead of pthread_create.


# 04f5329f 10-Mar-2006 David Xu <davidxu@FreeBSD.org>

Block all signals in helper threads except those should not be blocked.


# 3445f743 07-Mar-2006 David Xu <davidxu@FreeBSD.org>

Remove stale comments.


# c5a4f4ef 07-Mar-2006 David Xu <davidxu@FreeBSD.org>

1. Always call user callback function in newly created thread, it seems
POSIX implies that the user callback function must be executed in clean
environment.
2. Use newly introduced pthread stubs in l

1. Always call user callback function in newly created thread, it seems
POSIX implies that the user callback function must be executed in clean
environment.
2. Use newly introduced pthread stubs in libc.

show more ...


# 6348ace8 04-Mar-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 not

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.

show more ...


# 5f2252c2 02-Mar-2006 David Xu <davidxu@FreeBSD.org>

Fix a mutex lock/unlock mismatch.


# de86f235 01-Mar-2006 David Xu <davidxu@FreeBSD.org>

Forgot to revert to use weak symbols when I was debugging, fix it!


# 4acaec8f 01-Mar-2006 David Xu <davidxu@FreeBSD.org>

Bring in my initial version of POSIX realtime extension library.
Current the library implements mqueue, timer and aio with SIGEV_THREAD
notification supported.

Earlier version reviewed by: deischen


12