epoll十问之close

Q6  Will closing a file descriptor cause it to be removed from all epoll sets automatically?

       A6  Yes, but be aware of the following point.  A file descriptor is a reference to an open file description (see open(2)).  Whenever a descriptor is  duplicated  via  dup(2),
           dup2(2),  fcntl(2)  F_DUPFD,  or fork(2), a new file descriptor referring to the same open file description is created.  An open file description continues to exist until
           all file descriptors referring to it have been closed.  A file descriptor is removed from an epoll set only after all the file descriptors  referring  to  the  underlying
           open file description have been closed (or before if the descriptor is explicitly removed using epoll_ctl(2) EPOLL_CTL_DEL).  This means that even after a file descriptor
           that is part of an epoll set has been closed, events may be reported for that file descriptor if other file descriptors referring to the same underlying file  description
           remain open.

此外，看一看EPOLL_CTL_DEL

 EPOLL_CTL_ADD
              Register the target file descriptor fd on the epoll instance referred to by the file descriptor epfd and associate the event event with the internal file linked to fd.

       EPOLL_CTL_MOD
              Change the event event associated with the target file descriptor fd.

       EPOLL_CTL_DEL
              Remove (deregister) the target file descriptor fd from the epoll instance referred to by epfd.  The event is ignored and can be NULL (but see BUGS below).

   Questions and answers
       Q0  What is the key used to distinguish the file descriptors registered in an epoll set?

       A0  The key is the combination of the file descriptor number and the open file description (also known as an "open file handle", the kernel's internal  representation  of  an
           open file).

       Q1  What happens if you register the same file descriptor on an epoll instance twice?

       A1  You will probably get EEXIST.  However, it is possible to add a duplicate (dup(2), dup2(2), fcntl(2) F_DUPFD) descriptor to the same epoll instance.  This can be a useful
           technique for filtering events, if the duplicate file descriptors are registered with different events masks.

       Q2  Can two epoll instances wait for the same file descriptor?  If so, are events reported to both epoll file descriptors?

       A2  Yes, and events would be reported to both.  However, careful programming may be needed to do this correctly.

       Q3  Is the epoll file descriptor itself poll/epoll/selectable?

       A3  Yes.  If an epoll file descriptor has events waiting then it will indicate as being readable.

       Q4  What happens if one attempts to put an epoll file descriptor into its own file descriptor set?

       A4  The epoll_ctl(2) call will fail (EINVAL).  However, you can add an epoll file descriptor inside another epoll file descriptor set.

       Q5  Can I send an epoll file descriptor over a UNIX domain socket to another process?

       A5  Yes, but it does not make sense to do this, since the receiving process would not have copies of the file descriptors in the epoll set.

       Q6  Will closing a file descriptor cause it to be removed from all epoll sets automatically?

       A6  Yes, but be aware of the following point.  A file descriptor is a reference to an open file description (see open(2)).  Whenever a descriptor is  duplicated  via  dup(2),
           dup2(2),  fcntl(2)  F_DUPFD,  or fork(2), a new file descriptor referring to the same open file description is created.  An open file description continues to exist until
           all file descriptors referring to it have been closed.  A file descriptor is removed from an epoll set only after all the file descriptors  referring  to  the  underlying
           open file description have been closed (or before if the descriptor is explicitly removed using epoll_ctl(2) EPOLL_CTL_DEL).  This means that even after a file descriptor
           that is part of an epoll set has been closed, events may be reported for that file descriptor if other file descriptors referring to the same underlying file  description
           remain open.

       Q7  If more than one event occurs between epoll_wait(2) calls, are they combined or reported separately?

       A7  They will be combined.

       Q8  Does an operation on a file descriptor affect the already collected but not yet reported events?

       A8  You can do two operations on an existing file descriptor.  Remove would be meaningless for this case.  Modify will reread available I/O.

       Q9  Do I need to continuously read/write a file descriptor until EAGAIN when using the EPOLLET flag (edge-triggered behavior) ?

       A9  Receiving an event from epoll_wait(2) should suggest to you that such file descriptor is ready for the requested I/O operation.  You must consider it ready until the next
           (nonblocking) read/write yields EAGAIN.  When and how you will use the file descriptor is entirely up to you.

           For packet/token-oriented files (e.g., datagram socket, terminal in canonical mode), the only way to detect the end  of  the  read/write  I/O  space  is  to  continue  to
           read/write until EAGAIN.

           For  stream-oriented files (e.g., pipe, FIFO, stream socket), the condition that the read/write I/O space is exhausted can also be detected by checking the amount of data
           read from / written to the target file descriptor.  For example, if you call read(2) by asking to read a certain amount of data and read(2)  returns  a  lower  number  of
           bytes, you can be sure of having exhausted the read I/O space for the file descriptor.  The same is true when writing using write(2).  (Avoid this latter technique if you
           cannot guarantee that the monitored file descriptor always refers to a stream-oriented file.)