Hello, I have been trying to use the Kernel Connection Multiplexor (KCM) for request-level scheduling on top of TCP streams. The parent thread of a multi-threaded server creates and clones KCM sockets. It then listens for a pre-determined number of connections and attaches the connected sockets to the first KCM socket it created. Finally, it spins up threads that each uses one KCM socket to read() requests and write() responses. I observe that often the threads stop receiving, getting stuck in read(), a couple of seconds after the program start. This behavior is non-deterministic but it becomes more likely the more KCM sockets I create. Is there any known KCM bug or is this most likely an error from my side? I apologize in advance if this is not the right channel for this question. Best, Kostis
|