Attachment #42531
[1/5] DBusSocketSet: new abstraction for struct pollfd[] or whatever patch 2011-01-26 09:12:05 UTC 18.92 KB no flags Details
Attachment #42532
[2/5] Check for epoll in configure.ac patch 2011-01-26 09:12:26 UTC 1.39 KB no flags Details
Attachment #42533
[3/5] Add an implementation of DBusSocketSet using epoll patch 2011-01-26 09:12:45 UTC 9.42 KB no flags Details
Attachment #42534
[4/5] Add a stub _dbus_loop_toggle_watch and call it where needed patch 2011-01-26 09:13:00 UTC 7.82 KB no flags Details
Attachment #42535
[5/5] Maintain the set of polled sockets over time patch 2011-01-26 09:13:33 UTC 11.69 KB no flags Details
Attachment #42905
[6] Choose between poll and epoll at runtime patch 2011-02-03 10:34:07 UTC 18.83 KB no flags Details
Attachment #42906
[7] Use epoll in a backwards-compatible way on Linux < 2.6.27 patch 2011-02-03 10:34:35 UTC 2.29 KB no flags Details
Attachment #45390
[4/5 v2] Add a stub _dbus_loop_toggle_watch and call it where needed patch 2011-04-07 10:01:36 UTC 7.82 KB no flags Details
Attachment #47907
[PATCH 1/6] DBusSocketSet: new abstraction for struct pollfd[] or whatever patch 2011-06-13 09:31:50 UTC 23.09 KB no flags Details
Attachment #47908
[PATCH 2/6] Check for epoll in configure.ac patch 2011-06-13 09:32:11 UTC 1.46 KB no flags Details
Attachment #47909
[PATCH 3/6] Add an implementation of DBusSocketSet using epoll patch 2011-06-13 09:32:37 UTC 11.69 KB no flags Details
Attachment #47910
[PATCH 4/6] Add a stub _dbus_loop_toggle_watch and call it where needed patch 2011-06-13 09:32:56 UTC 7.90 KB no flags Details
Attachment #47911
[PATCH 5/6] Maintain the set of polled sockets over time patch 2011-06-13 09:33:17 UTC 11.76 KB no flags Details
Attachment #47912
[PATCH 6/6] Use epoll in a backwards-compatible way on Linux < 2.6.27 patch 2011-06-13 09:33:39 UTC 2.31 KB no flags Details
Attachment #53061
_dbus_loop_new: don't crash on OOM allocating socket set patch 2011-11-02 08:55:19 UTC 1.04 KB no flags Details

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.