comparison src/event/modules/ngx_win32_poll_module.c @ 7583:efd71d49bde0

Events: available bytes calculation via ioctl(FIONREAD). This makes it possible to avoid looping for a long time while working with a fast enough peer when data are added to the socket buffer faster than we are able to read and process them (ticket #1431). This is basically what we already do on FreeBSD with kqueue, where information about the number of bytes in the socket buffer is returned by the kevent() call. With other event methods rev->available is now set to -1 when the socket is ready for reading. Later in ngx_recv() and ngx_recv_chain(), if full buffer is received, real number of bytes in the socket buffer is retrieved using ioctl(FIONREAD). Reading more than this number of bytes ensures that even with edge-triggered event methods the event will be triggered again, so it is safe to stop processing of the socket and switch to other connections. Using ioctl(FIONREAD) only after reading a full buffer is an optimization. With this approach we only call ioctl(FIONREAD) when there are at least two recv()/readv() calls.
author Maxim Dounin <mdounin@mdounin.ru>
date Thu, 17 Oct 2019 16:02:19 +0300
parents 4089b3d2cb59
children
comparison
equal deleted inserted replaced
7582:70749256af79 7583:efd71d49bde0
378 if ((revents & POLLIN) && c->read->active) { 378 if ((revents & POLLIN) && c->read->active) {
379 found = 1; 379 found = 1;
380 380
381 ev = c->read; 381 ev = c->read;
382 ev->ready = 1; 382 ev->ready = 1;
383 ev->available = -1;
383 384
384 queue = ev->accept ? &ngx_posted_accept_events 385 queue = ev->accept ? &ngx_posted_accept_events
385 : &ngx_posted_events; 386 : &ngx_posted_events;
386 387
387 ngx_post_event(ev, queue); 388 ngx_post_event(ev, queue);