1. 04 Feb, 2020 1 commit
  2. 09 Dec, 2019 1 commit
  3. 19 Oct, 2019 1 commit
  4. 21 May, 2019 1 commit
  5. 17 Feb, 2019 3 commits
  6. 27 May, 2018 1 commit
  7. 26 May, 2018 1 commit
  8. 10 Mar, 2018 1 commit
    • Manuel Segura's avatar
      Pull request to merge porting to WindRiver VxWorks 6.x (#2966) · 4726f726
      Manuel Segura authored
      * Problem: Still need to port over more files to VxWorks 6.x
      
      Solution: Port more files to VxWorks 6.x
      
      * Problem: Need to port over remaining files to VxWorks 6.x. Also remove POSIX thread dependency for VxWorks (because of priority inversion problem in POSIX mutexes with VxWorks 6.x processes)
      
      Solution: Port over remaining files to VxWorks 6.x. Also removed POSIX thread dependency for VxWorks
      
      * Problem: Needed to modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x.
      
      Solution:  Modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x
      4726f726
  9. 12 Feb, 2018 1 commit
  10. 11 Feb, 2018 1 commit
  11. 02 Feb, 2018 1 commit
  12. 25 Oct, 2017 1 commit
    • f18m's avatar
      Change ZMQ_THREAD_AFFINITY to… · 2aa0e6fd
      f18m authored
      Change ZMQ_THREAD_AFFINITY to ZMQ_THREAD_AFFINITY_CPU_ADD/ZMQ_THREAD_AFFINITY_CPU_REMOVE. Avoid prefix thread names when no prefix was set.
      2aa0e6fd
  13. 16 Oct, 2017 1 commit
    • f18m's avatar
      Background threads enhancements (#2778) · bfbb4ff2
      f18m authored
      * Background thread scheduling 
      
      - add ZMQ_THREAD_AFFINITY ctx option; set all thread scheduling options
      from the context of the secondary thread instead of using the main
      process thread context!
      - change ZMQ_THREAD_PRIORITY to support setting NICE of the background
      thread when using SCHED_OTHER
      bfbb4ff2
  14. 12 Mar, 2017 1 commit
    • Luca Boccassi's avatar
      Problem: ZMQ background threads are unnamed · 3ab4796c
      Luca Boccassi authored
      Solution: use pthread API to set the name. For now call every thread
      "ZMQ b/g thread". Would be nice to number the I/O threads and name
      explicitly the reaper thread, but in reality a bit of internal API
      churn would be necessary, so perhaps it's not worth it.
      This is useful when debugging a process with many threads.
      3ab4796c
  15. 14 May, 2016 1 commit
  16. 25 Apr, 2016 1 commit
  17. 21 Feb, 2016 4 commits
  18. 28 Jan, 2016 1 commit
  19. 02 Jun, 2015 1 commit
  20. 22 Jan, 2015 1 commit
  21. 02 Jul, 2014 1 commit
  22. 02 Jan, 2014 1 commit
  23. 12 Mar, 2013 1 commit
    • Pieter Hintjens's avatar
      Removed corporate advertisements from source file headers · f0f16505
      Pieter Hintjens authored
      Copyrights had become ads for Sustrik's corporate sponsors, going against the original
      agreement to share copyrights with the community (that agreement was: one line stating
      iMatix copyright + one reference to AUTHORS file). The proliferation of corporate ads
      is also unfair to the many individual authors. I've removed ALL corporate title from
      the source files so the copyright statements can now be centralized in AUTHORS and
      source files can be properly updated on an annual basis.
      f0f16505
  24. 01 Nov, 2011 1 commit
  25. 31 Oct, 2011 1 commit
  26. 02 Mar, 2011 1 commit
  27. 13 Jan, 2011 1 commit
  28. 27 Nov, 2010 1 commit
  29. 30 Oct, 2010 1 commit
  30. 25 Aug, 2010 1 commit
    • Martin Sustrik's avatar
      WIP: Socket migration between threads, new zmq_close() semantics · 05d90849
      Martin Sustrik authored
      Sockets may now be migrated between OS threads; sockets may not be used by
      more than one thread at any time. To migrate a socket to another thread the
      caller must ensure that a full memory barrier is called before using the
      socket from the target thread.
      
      The new zmq_close() semantics implement the behaviour discussed at:
      
      http://lists.zeromq.org/pipermail/zeromq-dev/2010-July/004244.html
      
      Specifically, zmq_close() is now deterministic and while it still returns
      immediately, it does not discard any data that may still be queued for
      sending. Further, zmq_term() will now block until all outstanding data has
      been sent.
      
      TODO: Many bugs have been introduced, needs testing. Further, SO_LINGER or
      an equivalent mechanism (possibly a configurable timeout to zmq_term())
      needs to be implemented.
      05d90849
  31. 05 Jan, 2010 1 commit
  32. 29 Aug, 2009 1 commit
  33. 03 Aug, 2009 1 commit
  34. 29 Jul, 2009 1 commit