All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Ben <linux-kernel-junk-email@slimyhorror.com>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fw: epoll and fork()
Date: Tue, 02 Mar 2004 10:25:24 -0500	[thread overview]
Message-ID: <4044A764.1030304@nortelnetworks.com> (raw)
In-Reply-To: Pine.LNX.4.44.0403020654080.24044-100000@bigblue.dev.mdolabs.com

Davide Libenzi wrote:

> Sorry but what behaviour do you expect by unregistering an fd pushed by 
> the parent from inside a child? Events work exactly the same. Since the 
> context is shared, events are delivered only once.

For principle of least surprise, I would expect that the refcounts would 
be bumped up so that the child could deregister without affecting the 
parent.

Closing the fd in the child doesn't affect the fd in the parent. 
Removing an fd from an fd_set in the child doesn't affect the fd_set in 
the parent.  Unregistering an fd from an epoll set in the child 
shouldn't affect the parent either.

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


  reply	other threads:[~2004-03-02 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040302050233.3b33188b.akpm@osdl.org>
2004-03-02 15:05 ` Fw: epoll and fork() Davide Libenzi
2004-03-02 15:25   ` Chris Friesen [this message]
2004-03-03 10:38     ` Davide Libenzi
2004-03-02 15:38   ` Ben
2004-03-02 15:44     ` Mark Mielke
2004-03-03 10:29     ` Davide Libenzi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4044A764.1030304@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=akpm@osdl.org \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel-junk-email@slimyhorror.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.