How to signal select() to return immediately?

by

You are almost there. Use a “self-pipe” trick. Open a pipe, add it to your select() read and write fd_set, write to it from main thread to unblock a worker thread. It is portable across POSIX systems.

I have seen a variant of similar technique for Windows in one system (in fact used together with the method above, separated by #ifdef WIN32). Unblocking can be achieved by adding a dummy (unbound) datagram socket to fd_set and then closing it. The downside is that, of course, you have to re-open it every time.

However, in the aforementioned system, both of these methods are used rather sparingly, and for unexpected events (e.g., signals, termination requests). Preferred method is still a variable timeout to select(), depending on how soon something is scheduled for a worker thread.

More Related Contents:

  1. Is it possible to access/update the child thread’s resource from parent thread?
  2. Using select() for non-blocking sockets
  3. What’s the correct answer about getservbyname?
  4. How do I start threads in plain C?
  5. How do I change a TCP socket to be non-blocking?
  6. When the main thread exits, do other threads also exit?
  7. Wake up thread blocked on accept() call
  8. Sending file descriptor by Linux socket
  9. Signal handling with multiple threads in Linux
  10. Error: Address already in use while binding socket with address but the port number is shown free by `netstat`
  11. Turn a simple socket into an SSL socket
  12. Socket accept – “Too many open files”
  13. Is there a way to flush a POSIX socket?
  14. Using sys/socket.h functions on windows
  15. What are the differences between poll and select?
  16. Bind failed: Address already in use
  17. Receiving multiple multicast feeds on the same port – C, Linux
  18. socket connect() vs bind()
  19. Writing to a closed, local TCP socket not failing
  20. Boost::asio – how to interrupt a blocked tcp server thread?
  21. fork and existing threads?
  22. Pthread Run a thread right after it’s creation
  23. Using C/Pthreads: do shared variables need to be volatile?
  24. Is accept() thread-safe?
  25. Linux/POSIX equivalent for Win32’s CreateEvent, SetEvent, WaitForSingleObject
  26. Multiple threads and CPU cache
  27. c++ how to use select to see if a socket has closed
  28. Is it possible (and safe) to make an accepting socket non-blocking?
  29. How to reset a socket back to blocking mode (after I set it to nonblocking mode)?
  30. WaitForSingleObject and WaitForMultipleObjects equivalent in Linux?

Leave a Comment