Thanks very much for the comments. I've changed those; the banners and renamed Wait4Poller. I've tried it with my "sleeps" it solves what I could provoke. (I don't know how to reproduce the original production-system problem, as that seems to be quite rare).

Repackaging as a separate class is likely a better way to make it. However I'm not sure I can find a nice general interface for it. (It would probably be used with an epoll-poller, as eventfd is linux specific like epoll). I don't think we have the same problem in XrdSysIOEventsPollE because of how that poller works. So I propose to leave it here (not separated into another class) now.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/1941#issuecomment-1458431043", "url": "https://github.com/xrootd/xrootd/pull/1941#issuecomment-1458431043", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1