Hello, Note that this is my understanding of how it works, but I am not a core dev so I am not sure. I may be totally wrong.
If the IO thread does not run because of not enough CPU time I guess a lot of thing can go wrong. As far as I know, messages go through the IO thread for dispatching. The I/O thread not running could then could prevent you from both sending and receiving message. As for your second question, I do not know. If your application as long running one, you could try to manually change the priority of the threads and see if it fixes your problem. On Mon, Jun 8, 2015 at 12:30 PM, Leonard Michelet <[email protected]> wrote: > Hello, I use ZeroMQ on a Preempt_rt kernel and I have some connection problem > on a virtual machine. > I run automated tests on this virtual machine and its CPU is quite busy, and > I noticed that my real time application, which use zmq, has 2 threads not > with real time scheduler, but time shared. > These thread are usually in "epoll_wait" kernel's function, and I suppose > it's internal thread created by ZeroMQ (I set ZMQ_IO_THREADS to 1). > I would like to know what is the purpose of these thread, to understand what > symptoms I could have if these thread were never run because of not enough > CPU time. > Would it prevent me from receiving message? Would it prevent me to send > message? Both? > > And my next question would be : is there a way to set priority on these > thread? > > Thanks for reading. > Léonard. > > P.S : the application set real time priority using pthread_setschedparam > which is a per thread setting, so it doesn't change the defaullt priority of > new thread, and we would like to avoid setting such a default. > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev -- Kapp Arnaud - Xaqq _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
