asio changeset 48031 - cpu spike fix (hopefully)

This commit is contained in:
Marcos Pinto 2008-08-13 02:37:14 +00:00
parent 07f65d8a22
commit fe2b8bf5d4
2 changed files with 16 additions and 16 deletions

View File

@ -421,15 +421,15 @@ private:
more_writes = write_op_queue_.perform_operation(descriptor, ec);
else
more_writes = write_op_queue_.has_operation(descriptor);
if ((events[i].events == POLLHUP)
if ((events[i].events & (POLLERR | POLLHUP)) != 0
&& (events[i].events & ~(POLLERR | POLLHUP)) == 0
&& !more_except && !more_reads && !more_writes)
{
// If we have only an POLLHUP event and no operations associated
// with the descriptor then we need to delete the descriptor from
// /dev/poll. The poll operation might produce POLLHUP events even
// if they are not specifically requested, so if we do not remove the
// descriptor we can end up in a tight polling loop.
// If we have an event and no operations associated with the
// descriptor then we need to delete the descriptor from /dev/poll.
// The poll operation can produce POLLHUP or POLLERR events when there
// is no operation pending, so if we do not remove the descriptor we
// can end up in a tight polling loop.
::pollfd ev = { 0 };
ev.fd = descriptor;
ev.events = POLLREMOVE;

View File

@ -495,15 +495,15 @@ private:
more_writes = write_op_queue_.perform_operation(descriptor, ec);
else
more_writes = write_op_queue_.has_operation(descriptor);
if ((events[i].events == EPOLLHUP)
if ((events[i].events & (EPOLLERR | EPOLLHUP)) != 0
&& (events[i].events & ~(EPOLLERR | EPOLLHUP)) == 0
&& !more_except && !more_reads && !more_writes)
{
// If we have only an EPOLLHUP event and no operations associated
// with the descriptor then we need to delete the descriptor from
// epoll. The epoll_wait system call will produce EPOLLHUP events
// even if they are not specifically requested, so if we do not
// remove the descriptor we can end up in a tight loop of repeated
// If we have an event and no operations associated with the
// descriptor then we need to delete the descriptor from epoll. The
// epoll_wait system call can produce EPOLLHUP or EPOLLERR events
// when there is no operation pending, so if we do not remove the
// descriptor we can end up in a tight loop of repeated
// calls to epoll_wait.
epoll_event ev = { 0, { 0 } };
epoll_ctl(epoll_fd_, EPOLL_CTL_DEL, descriptor, &ev);