Backporting high cpu usage fix in wayland from upstream 72/2772/1 accepted/2.0alpha-wayland/20130227.211101 submit/2.0alpha-wayland/20130220.232504
authorJimmy Huang <jimmy.huang@intel.com>
Wed, 20 Feb 2013 23:20:39 +0000 (15:20 -0800)
committerJimmy Huang <jimmy.huang@intel.com>
Wed, 20 Feb 2013 23:20:39 +0000 (15:20 -0800)
commit6806d7eeea6edcc55790842608adb5cec01b3277
tree9eb1ff9b1f906787733df1f85d5dd910ad1dd735
parent80ff555b2270c92f6a32ddca04a3f7c9e71dc251
Backporting high cpu usage fix in wayland from upstream

Backporting 81360

ecore-wayland: (version 2)Fix monitoring ECORE_FD_WRITE

defaultly on wayland display fd lead to 100% cpu usage

In ecore_wl_init(), adding wayland display fd with ECORE_FD_WRITE
flag make CPU usage 100%. The proper way to monitor the ECORE_FD_WRITE
is when the wl_display_flush() return value < 0 and errno == EAGAIN.
And if wl_display_flush() return, we remove ECORE_FD_WRITE flag from
the display fd.

Change from v1:
Add idle enterer destroy code into _ecore_wl_shutdown() to avoid
using freed wl_display.

Signed-off-by: Jimmy Huang <jimmy.huang@intel.com>
src/lib/ecore_wayland/Ecore_Wayland.h
src/lib/ecore_wayland/ecore_wl.c