[lkml]   [2007]   [Oct]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: epoll design problems with common fork/exec patterns
    On Sat, Oct 27, 2007 at 12:23:52PM +0200, Eric Dumazet <> wrote:
    > > Q6 Will the close of an fd cause it to be removed from all epoll
    > > sets automatically?
    > > A6 Yes.
    > Answer : epoll documentation cannot explain the full semantic of file

    epoll documentation easily can. there is nothig keeping it from it. don't
    make silly arguments like that.

    > Or should, since you had problems

    You are again implying I lakc understanding. That is, however, not true.
    I don't see the point in being insulted by you, so I won'T continue
    talking to you :(

    > The 'close' of a file is not close(fd) :)

    Good that you understand that.

    That is one of my problems, as the manpage talks about closing of the fd,
    but there are multiple ways to do that, and some are not handled the same

    > epoll has to deal with files, but documentation is a User side
    > documentation, so has to use 'file descriptors'.

    There is obviously no need for documentation to do that, contrary to your
    claim. The manpages for e.g. dup or the official sus manpages manage to
    document it (mostly) correctly, so your claim that documentation must use
    file descriptors when the underlying file structure is meant is disproven.

    > fork() is acting sort of dup() , as it increases all file refcounts.
    > You have problems about close()/dup()/fork()/... file descriptors semantic,
    > which is handled by a layer independent from epoll stuff.

    No, I have no problem with dup at all.

    I have a problem with explicitlx closing file descriptors in the child will
    stop events for those files to be reported in the parent.

    I am sorry, but I epxlained this very clearly a number of times, but for some
    reason, apart from accusing me to not understanding files and file
    descritpors or (clear enough) documentation, you ignore that and instead
    hammer on other problems.

    To me, it seems you are not the one who understands.

    The choice of a Deliantra, the free code+content MORPG
    -----==- _GNU_
    ----==-- _ generation
    ---==---(_)__ __ ____ __ Marc Lehmann
    --==---/ / _ \/ // /\ \/ /
    -=====/_/_//_/\_,_/ /_/\_\
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-10-27 12:49    [W:0.030 / U:16.180 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site