Mercurial > hg > nginx
comparison src/event/ngx_event_openssl.c @ 7617:f1720934c45b
SSL: reworked posted next events again.
Previous change 1ce3f01a4355 incorrectly introduced processing of the
ngx_posted_next_events queue at the end of operation, effectively making
posted next events a nop, since at the end of an event loop iteration
the queue is always empty. Correct approach is to move events to the
ngx_posted_events queue at an iteration start, as it was done previously.
Further, in some cases the c->read event might be already in the
ngx_posted_events queue, and calling ngx_post_event() with the
ngx_posted_next_events queue won't do anything. To make sure the event
will be correctly placed into the ngx_posted_next_events queue
we now check if it is already posted.
author | Maxim Dounin <mdounin@mdounin.ru> |
---|---|
date | Fri, 27 Dec 2019 19:43:01 +0300 |
parents | 1ce3f01a4355 |
children | 8409f9df6219 5d91389e0fd3 |
comparison
equal
deleted
inserted
replaced
7616:fd4d2155d3e6 | 7617:f1720934c45b |
---|---|
2014 */ | 2014 */ |
2015 | 2015 |
2016 if (c->read->available < 0) { | 2016 if (c->read->available < 0) { |
2017 c->read->available = 0; | 2017 c->read->available = 0; |
2018 c->read->ready = 0; | 2018 c->read->ready = 0; |
2019 | |
2020 if (c->read->posted) { | |
2021 ngx_delete_posted_event(c->read); | |
2022 } | |
2019 | 2023 |
2020 ngx_post_event(c->read, &ngx_posted_next_events); | 2024 ngx_post_event(c->read, &ngx_posted_next_events); |
2021 } | 2025 } |
2022 | 2026 |
2023 ngx_log_debug1(NGX_LOG_DEBUG_EVENT, c->log, 0, | 2027 ngx_log_debug1(NGX_LOG_DEBUG_EVENT, c->log, 0, |