From 40d61f55ac53e3cd2f229d0b032da03032e3d53d Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Thu, 7 Jan 2010 00:37:57 -0800 Subject: POSIX_MQ#notify block execution on message received This is implementation uses both a short-lived POSIX thread and a pre-spawned Ruby Thread in a manner that works properly under both Ruby 1.8 (green threads) and 1.9 (where Ruby Threads are POSIX threads). The short-lived POSIX thread will write a single "\0" byte to a pipe the Ruby Thread waits on. This operation is atomic on all platforms. Once the Ruby Thread is woken up from the pipe, it will execute th block given to it. This dual-thread implementation is inspired by the way glibc implements mq_notify(3) + SIGEV_THREAD under Linux where the kernel itself cannot directly spawn POSIX threads. --- README | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'README') diff --git a/README b/README index c7b65cb..5be5478 100644 --- a/README +++ b/README @@ -11,7 +11,8 @@ network-aware message queue implementations. == Features -* Supports message notifications via signals. +* Supports message notifications via signals and block execution + in a separate thread. * Supports portable non-blocking operation. Under Linux 2.6.6+ and FreeBSD 7.2+, POSIX_MQ objects may even be used with event @@ -19,7 +20,8 @@ network-aware message queue implementations. * Optional timeouts may be applied to send and receive operations. -* Thread-safe under Ruby 1.9, releases GVL before blocking operations. +* Thread-safe blocking operations under Ruby 1.9, releases GVL + before blocking operations. * Documented library API -- cgit v1.2.3-24-ge0c7