poll/epoll 会阻塞吗?它与异步IO有什么不同?
我一直认为 poll/epoll 不会阻塞。这就是 Nginx 等非阻塞服务器使用它们的原因。
但在这个Stackoverflow问题中,多次提到了轮询阻塞。
那么poll/epoll会阻塞吗?
poll/epoll 与 async IO 有何不同?
I was always under the impression that poll/epoll doesn't block. That's why they are used by non-blocking servers such as Nginx.
But in this Stackoverflow question it was stated several times that poll blocks.
So does poll/epoll block?
And how is poll/epoll different from async IO?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
是的,poll/epoll 块。分派线程来服务客户端的服务器通常无法像使用 epoll 等 I/O 事件通知模型的服务器那样扩展。 poll 比 epoll 更旧且效率更低(O(n) vs O(1))。
[更新]
Nginx 不是非阻塞的。当请求到来时,epoll_wait 正在等待的事件之一会收到通知,并且对 epoll_wait 的调用将返回。然后 Nginx 循环遍历为每个事件提供服务的信号事件。 Nginx 源代码可以在这里找到... http://nginx.org/download/nginx-1.1。 1.tar.gz
看一下 nginx-1.1.1\src\event\modules\ngx_epoll_module.c 中的
ngx_epoll_process_events
函数[UPDATE2]
另请参阅epoll_wait(2) 的手册页 ... http://linux.die.net/man/2/epoll_wait
[UPDATE3]
为了向自己证明 Nginx / epoll 会阻塞,请在 Linux 上尝试这个...
./configure --with-debug
(注意:我有添加 libpcre3-dev)make
sudo make install
/usr/local/nginx/sbin/nginx
(注意:我有杀死阿帕奇首先sudo /etc/init.d/apache2 stop
)sudo gdb
文件 /usr/local/nginx/sbin/nginx
b ngx_epoll_module.c:531(设置断点)
ps -ef | grep nginx
并在 gdb 中使用 nginx 工作进程(不是主进程)的 PIDattach
您可能需要
继续
几次,但它最终应该会阻塞。然后打开浏览器并转到 http://localhost ...调试器应该在epoll_wait
返回后立即中断。Yes, poll/epoll block. Servers that spin off threads to service clients typically don't scale as well as servers that use an I/O event notification model like epoll. poll is older and less efficient than epoll (O(n) vs O(1)).
[UPDATE]
Nginx is not non-blocking. When a request comes in, one of the events epoll_wait is waiting for is notified and the call to epoll_wait returns. Then Nginx loops through the signaled events servicing each one. The Nginx source code is available here ... http://nginx.org/download/nginx-1.1.1.tar.gz
Take a look at the
ngx_epoll_process_events
function in nginx-1.1.1\src\event\modules\ngx_epoll_module.c[UPDATE2]
See also the man page for epoll_wait(2) ... http://linux.die.net/man/2/epoll_wait
[UPDATE3]
To prove to yourself that Nginx / epoll blocks, try this on Linux...
./configure --with-debug
(NOTE: I had to add libpcre3-dev)make
sudo make install
/usr/local/nginx/sbin/nginx
(NOTE: I had to kill apache firstsudo /etc/init.d/apache2 stop
)sudo gdb
file /usr/local/nginx/sbin/nginx
b ngx_epoll_module.c:531
(to set a break point)ps -ef | grep nginx
and use the PID of the nginx worker process (not the master)attach <PID of nginx worker>
continue
to resume the processYou may have to
continue
a couple times but it should eventually block. Then open a browser and go to http://localhost ... the debugger should then break right afterepoll_wait
returns.