On Tuesday 07 April 2015 15:16:34 Light, John J wrote: > I wasn?t going to mention that, but now that you did... > > The only CPU intensive parts of IoTivity are DTLS and (less so) PDU > creation. The I/O is only mildly overlapped. > > The need for multiple threads isn't performance or throughput. There's a > small latency play, but I don't think it's critical. > > If you believe me on that, the only reasons we have threads at all are: > * disconnect the application from the I/O, and > * as a crutch to separate function. > > The former is worthy, and we should preserve it when threads are available. > The other isn't, and only complicate maintenance, bug fix, and adding new > capabilities.
I don't agree with the former either. I don't mind it being there, but I dispute it being a necessity. The topic of this thread is now "event loop", which means integrating into single-thread event loops. Once that exists, we no longer need threads. We can still use them, but we won't need them. > If we eliminated most of the threading, we could drop glib and have a better > code base going forward. Agreed. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
