Matthieu Herrb <matth...@herrb.eu> writes: > this doesn't fix an issue I'm seeing on OpenBSD with xterm not beeing > able to start (it makes the X server spin at 100% CPU in > WaitForSomething()), while Jeremy's patches do fix the issue for me.
I think Jeremy's patch will cause the server to spin while any client is not writable, which isn't good. > I've not been able to really understand the issue yet, but that's a > data point. (And I'm glad to see that it doesn't seem to be an OpenBSD > specific issue :) I'd bet anyone using poll(2) instead of epoll(2) will see the same problems. It should be possible to reproduce this on Linux by using the poll path instead of epoll. -- -keith
Description: PGP signature
_______________________________________________ firstname.lastname@example.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel