On 12/20/2013 04:23 PM, Yin Kangkai wrote: Hi!
Sorry for late response, I've been out of office the last week(s). > On 2013-11-21, 12:33 +0100, Karol Lewandowski wrote: >> +TESTS >> +===== >> + >> +* Build test binaries: >> + >> + cd gio/tests >> + make >> + >> +* Set variable to use custom library and to use kdbus as session bus: >> + >> + export LD_LIBRARY_PATH=absolute_path_to_glib_libs_with_kdbus_patch >> + export DBUS_SESSION_BUS_ADDRESS=kdbus:path=/dev/kdbus/0-kdbus/bus >> + >> +* Run test binary server in terminal 1: >> + >> + ./gdbus-example-kdbus-server >> + >> +* Run test binary client in terminal 2: >> + >> + ./gdbus-example-kdbus-client >> + >> +* Sample client app output: >> + >> + elapsed time : 0.265072 s >> + elapsed time : 0.264353 s >> + elapsed time : 0.305062 s >> + elapsed time : 0.343710 s >> + elapsed time : 0.451501 s >> + elapsed time : 1.109851 s >> + elapsed time : 8.278217 s > > Will it be more interesting to show some real benchmarking numbers? ;) > > - results with vanilla GIO; > - results with GIO with kdbus transport, talking to kdbus > dbus-daemon; > - results with GIO with kdbus transport, talking through systemd-bus-proxyd > to systemd-bus-driverd; I agree this is very much needed. Currently, due to major changes in kdbus, we are redoing some of the gio-kdbus stuff again. Lukasz Skalski will share result in following days. Cheers, Karol _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel