The man page of epoll has a sample code for edge triggered like the following :
for (;;) {
nfds = epoll_wait(epollfd, events, MAX_EVENTS, -1);
if
As long as you read until you get an EAGAIN
error, you will get the event the next time you are calling epoll_wait
.
The event is only triggered when there is a change between empty and non-empty (or full and non-full for EPOLLOUT
), but that status then remains until the event is delivered via epoll_wait
.
On a somewhat related note: if you register for EPOLLIN
and EPOLLOUT
events and assuming you never fill up the send buffer, you still get the EPOLLOUT
flag set in the event returned by epoll_wait
each time EPOLLIN
is triggered - see https://lkml.org/lkml/2011/11/17/234 for a more detailed explanation.
And finally, the exact behaviour of edge-triggered mode actually depends on the socket type used and isn't really documented anywhere. I did some tests some time ago and documented my findings here: http://cmeerw.org/blog/753.html#753 - in short, for datagram sockets you might get more events than you would expect.
when you use Edge Triggered under epoll, read some thing, can like this
int n = -1;
while (1)
{
n = recv(fd, iobuf, init_buff_size, MSG_DONTWAIT);
if (n > 0)
{
LOG(glogfd, LOG_TRACE, "fd[%d] recv len %d\n", fd, n);
mybuff_setdata(&(curcon->recv_buff), iobuf, n); // this is my func
if (n == init_buff_size)
{
LOG(glogfd, LOG_DEBUG, "fd[%d] need recv nextloop %d\n", fd, n);
continue;
}
break;
}
if (n == 0)
{
LOG(glogfd, LOG_ERROR, "fd[%d] close %s:%d!\n", fd, ID, LN);
return do_close(fd);
}
if (errno == EINTR)
{
LOG(glogfd, LOG_TRACE, "fd[%d] need recv again!\n", fd);
continue;
}
else if (errno == EAGAIN)
{
LOG(glogfd, LOG_TRACE, "fd[%d] need recv next!\n", fd);
modify_fd_event(fd, EPOLLIN); // this is the KEY, add read again
break;
}
else
{
LOG(glogfd, LOG_ERROR, "fd[%d] close %s:%d!\n", fd, ID, LN);
return do_close(fd);
}
}