connection starvation problem

[xinghua_hi]

hi:

In man epoll , a section refer to "epoll edge trigger starvation problem", and around to this we need to maintain a ready list instead of read socket
until EAGAIN. but i didn't find any related solution code in nginx. In request body read function `ngx_http_do_read_client_request_body`, it seems that
nginx will read socket buffer until EAGAIN or has read Content-length data. so if a client is fast enough and post data is large enough, is it possible to
starve other connections? SO do i miss something important? nginx how to deal with this situation in read and write?

thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20140526/7124aed1/attachment.html>