Unnamed repository; edit this file 'description' to name the repository. https://cgit.space/~steering/inspircd++.git/atom/src/socketengines/socketengine_epoll.cpp?h=v3.0.0a2 2017-07-12T13:25:28Z 2017-07-12T13:25:28Z Peter Powell 2017-07-12T13:25:28Z urn:sha1:f471083cd0519d47c7c7a09029813ede41994f7b Merge v2.0.23 and v2.0.24 into master. 2017-07-11T12:22:02Z Robin Burchell 2017-03-22T16:59:08Z urn:sha1:8e8b0719bf58e2d875c06698f86377189da87e16 The write counters were close to useless because they were only incremented on a write "event" which is only triggered when writing would block. Read handling was a little more useful in that all reads must happen through the socket engine, so these were happening at the correct time, but we can clean this up by doing it in the SE itself rather than each platform port. This means that both read and write events are now easily and usefully defined as "a syscall of either read or write was attempted". We also count empty read and write events as being an event, because they still were an attempt to poll a socket in some way. This may help to identify "bad" code which is repeatedly trying to read a socket for some reason. Lastly, we check for failed read/write calls, and log them as an error event. A lot of the time, this is how sockets are determined as being disconnected (ie. at read/write time). While we're at it, split Update() in two to make the calls more self-describing. This has no real impact since only one call is made at a time anyway. 2017-07-09T21:45:00Z Peter Powell 2017-07-09T21:36:40Z urn:sha1:c0aba5b728b0a921d95ec120aa638dab1520b42f 2016-11-22T13:49:43Z Adam 2016-11-22T01:56:39Z urn:sha1:7ddef68f44ecb01f891e55a680078f7857fb866f 2016-08-11T08:56:47Z Attila Molnar 2016-08-11T08:56:47Z urn:sha1:f09ca8cf45a23680c16aab9068fb42f761098a93 2015-04-12T14:20:13Z Attila Molnar 2015-04-12T14:20:13Z urn:sha1:612384b3d46d06eea6fd71ee6dc60471d0f9e3d1 Remove enum EventType 2014-06-14T13:30:14Z Attila Molnar 2014-06-14T13:30:14Z urn:sha1:82435b6fa8805baa65e04a582f3e4a2c84237f73 2014-06-07T11:47:26Z Attila Molnar 2014-06-07T11:47:26Z urn:sha1:5a6fd54f8fd217232f98804431928609580742bc Do not exit if we can't determine it 2014-06-07T11:33:50Z Attila Molnar 2014-06-07T11:33:50Z urn:sha1:76f1ba946972dbff089b27d64748afc1c0d95c6a From man epoll: Since Linux 2.6.8, the size argument is unused, but must be greater than zero. (The kernel dynamically sizes the required data structures without needing this initial hint.) 2014-06-07T11:30:14Z Attila Molnar 2014-06-07T11:30:14Z urn:sha1:30fec322809582f91be70cc1bb16c9678180db76 We can cope with fds greater than SocketEngine::GetMaxFds() since 3752b3f59d5216d7dc6221a361efc76b9ad2273d