Re: epoll and shared fd's

From: Michael Kerrisk
Date: Thu Feb 28 2008 - 07:11:00 EST


On Tue, Feb 26, 2008 at 7:16 PM, Bodo Eggert <7eggert@xxxxxx> wrote:
> Michael Kerrisk <mtk.manpages@xxxxxxxxxxxxxx> wrote:
>
> > a) I did a
> >
> > s/internal kernel handle/open file description/
> >
> > since that is the POSIX term for the internal handle.
> >
> > b) It seems to me that you text doesn't quite make the point explicit
> > enough. I've tried to rewrite it; could you please check:
> >
> > A6 Yes, but be aware of the following point. A file
> > descriptor is a reference to an open file descrip-
> > tion (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. The
> > epoll interface automatically removes a file
> > descriptor from an epoll set only after all the
> > file descriptors referring to the underlying open
> > file handle have been closed. 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.
> >
> > Does that seem okay? I plan to include the text in man-pages-2.79.
>
> It's hard to read for me, and probably very hard to read for others.

Bodo,

I'm just reviewing this text, trying to see if I can improve it. At
the moment, I'm a little stuck. can you say a little more about why
you find it hard to read? that may help me improve it.

Cheers,

Michael


--
Michael Kerrisk
Maintainer of the Linux man-pages project
http://www.kernel.org/doc/man-pages/
Want to report a man-pages bug? Look here:
http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/