mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-02-03 16:31:08 +01:00
The channel can disable reading from the stream-interface using various methods, such as : - CF_DONT_READ - !channel_may_recv() - and possibly others Till now this was done by mangling SI_FL_RX_WAIT_EP which is not appropriate at all since it's not the stream interface which decides whether it wants to deliver data or not. Some places were also wrongly relying on SI_FL_RXBLK_ROOM since it was the only other alternative, but it's not suitable for CF_DONT_READ. Let's use the SI_FL_RXBLK_CHAN flag for this instead. It will properly prevent the stream interface from being woken up and reads from subscribing to more receipt without being accidently removed. It is automatically reset if CF_DONT_READ is not set in stream_int_notify(). The code is not trivial because it splits the logic between everything related to buffer contents (channel_is_empty(), CF_WRITE_PARTIAL, etc) and buffer policy (CF_DONT_READ). Also it now needs to decide timeouts based on any blocking flag and not just SI_FL_RXBLK_ROOM anymore. It looks like this patch has caused a minor performance degradation on connection rate, which possibly deserves being investigated deeper as the test conditions are uncertain (e.g. slightly more subscribe calls?).