Date: Thu, 21 Dec 2017 19:16:25 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 223530] devel/libepoll-shim: Update version Message-ID: <bug-223530-7141-15ytzObUsd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-223530-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-223530-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223530 Jan Kokem=C3=BCller <jan.kokemueller@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan.kokemueller@gmail.com --- Comment #10 from Jan Kokem=C3=BCller <jan.kokemueller@gmail.com> --- I'm the original author of the epoll-shim library. Please, if you have improvements to the library, or are seeing a bug, post an issue or PR on Gi= thub -- I've seen the freebsd-desktop branch and merged it almost a year ago. The original reason for this lib was really just supporting libinput. I've tried to port libinput to kqueue/kevent directly, but then I thought a small epoll wrapper would be better -- the code changes to upstream could be kept= to a minimum. Also, more Wayland related projects use epoll, so in theory they should 'ju= st work' with this library. I haven't really tried to get Wayland to work yet = on my side, but it is definitely also a goal of this library. For example, I've added support for polling a DRM device. In FreeBSD, those devices don't sup= port kqueue yet, just poll, and therefore require a special hack in epoll-shim. In general, the library should be quite useful if you need epoll as long as= you don't do anything too fancy. That said, there are still some limitations: - forget fork/exec behavior as in Linux... - no edge triggering or other 'fancy' flags (EPOLLET, EPOLLONESHOT, EPOLLEXCLUSIVE...) - no eventfd support yet (but who uses this, anyway?) - there is just support for _one_ poll/DRM device per process (yes, I know it's currently a giant hack but it seemed to work). - I define 'read' and 'close' macros that point to functions of the library because signalfd and timerfd need some special handling. This is ugly, but I haven't found a more elegant way yet. This means that you cannot really call vanilla 'read'/'close' on timer- and signalfds in some other translation un= it and expect everything to keep working properly. Luckily, libinput does not = do this. - Each timerfd spawns a thread doing some custom timer/signal stuff because EVFILT_TIMER does not really support the itimer interface very well. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-223530-7141-15ytzObUsd>