<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> I am interested if anyone has put together (or can offer) a recipe or pointers for implementing an alternate transport for DBus?<o:p></o:p> <o:p> </o:p> I have managed to port DBus to QNX and did some benchmarking on that platform. Unfortunately, QNX does not offer abstract sockets or any optimizations in the kernel to accelerate local (unix domain) sockets. As a result, to communicate between a client and a service via the DBus daemon requires several process hops and corresponding context switches. This kills performance as the number of processes increases and the network stack soaks up all available CPU cycles.<o:p></o:p> <o:p> </o:p> Fortunately, QNX offers a very efficient micro-kernel and message passing system for inter-process communication. This framework does not incur the overhead associated with the local socket implementation. What I’d like to do is provide an alternative transport that utilizes this (native) messaging passing framework. Unfortunately, I’m not real sure where to start.<o:p></o:p> <o:p> </o:p> It appears that some consideration has already been given to abstracting the underlying transport layer for DBus. Ideally, I *think* I’d like to add another <listen> option to the system/session, like<o:p></o:p> <o:p> </o:p> <listen>qnx:path=/blah</listen><o:p></o:p> <o:p> </o:p> With this configured, the QNX message passing transport needs to be instantiated.<o:p></o:p> <o:p> </o:p> So, what files/interfaces really need to be tweaked and/or added? Can anyone offer any suggestions or guidance? Please provide as much detail as you can offer.<o:p></o:p> <o:p> </o:p> Thanks . . .<o:p></o:p> </div> </body> </html>