public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Varshavchik <mrsam-W1w4QoW4mIDgLSHwZvcCBg@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: "Michael Kerrisk"
	<mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>,
	"Davide Libenzi"
	<davidel-AhlLAIvw+VEjIGhXcJzhZg@public.gmane.org>,
	"Chris ¥¯ Heath" <chris-FSXMH2gLahXJKwlM9GxbOw@public.gmane.org>,
	"David Schwartz" <davids-Rrbileazn+l54TAoqtyWWQ@public.gmane.org>,
	dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org,
	"Linux-Kernel@Vger. Kernel. Org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: epoll design problems with common fork/exec patterns
Date: Sun, 02 Mar 2008 10:11:57 -0500	[thread overview]
Message-ID: <cone.1204470717.369031.30230.500@commodore.email-scan.com> (raw)
In-Reply-To: cfd18e0f0802291154j612b4238i66cb8323b72814ca@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 677 bytes --]

Hijacking this epoll thread, the following related question occurs to me:

#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 re-read available I/O.

Why is EPOLL_CTL_DEL considered meaningless? A process is wrapping up its 
business and is preparing to remove the fd from the epoll set, and then 
close the file descriptor itself. In the meantime, the fd became readable, 
and a POLLIN event gets collected. So, what happens to the collected event, 
when the EPOLL_CTL_DEL operation is made?


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-03-02 15:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MDEHLPKNGKAHNMBLJOLKAEHCHNAC.davids@webmaster.com>
     [not found] ` <Pine.LNX.4.64.0710291147180.3387@alien.or.mcafeemobile.com>
     [not found]   ` <Pine.LNX.4.64.0710291147180.3387-GPJ85BhbkB8RepQJljzAVbITYcZ0+W3JAL8bYrjMMd8@public.gmane.org>
2008-02-26 15:13     ` epoll design problems with common fork/exec patterns Michael Kerrisk
     [not found]       ` <47C42CA7.4030607-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-02-26 18:51         ` Davide Libenzi
     [not found]           ` <Pine.LNX.4.64.0802261049040.27243-GPJ85BhbkB8RepQJljzAVbITYcZ0+W3JAL8bYrjMMd8@public.gmane.org>
2008-02-27  1:30             ` Chris "ク" Heath
     [not found]               ` <1204075804.5238.7.camel-DBi1IKlRe8YXiSwHZUBl+UgmxNRb6L7S@public.gmane.org>
2008-02-27 19:35                 ` Davide Libenzi
     [not found]                   ` <Pine.LNX.4.64.0802271131180.377-GPJ85BhbkB8RepQJljzAVbITYcZ0+W3JAL8bYrjMMd8@public.gmane.org>
2008-02-28 13:12                     ` Michael Kerrisk
     [not found]                       ` <cfd18e0f0802280512q43a457d0sc9a8dc83c51e8e1c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-02-28 13:23                         ` Michael Kerrisk
     [not found]                           ` <cfd18e0f0802280523p1bdacfc5s274387f8280238c8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-02-28 19:34                             ` Davide Libenzi
2008-02-28 19:23                         ` Davide Libenzi
     [not found]                           ` <Pine.LNX.4.64.0802281106050.7660-GPJ85BhbkB8RepQJljzAVbITYcZ0+W3JAL8bYrjMMd8@public.gmane.org>
2008-02-29 15:46                             ` Michael Kerrisk
     [not found]                               ` <cfd18e0f0802290746p3cb7efc9j72394cd77ff37829-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-02-29 19:19                                 ` Davide Libenzi
2008-02-29 19:54                                   ` Michael Kerrisk
2008-03-02 15:11                                     ` Sam Varshavchik [this message]
     [not found]                                       ` <cone.1204470717.369031.30230.500-lO+bjgoT4TKm14v+eVDVcBDJ/jce7dRH@public.gmane.org>
2008-03-02 21:44                                         ` 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=cone.1204470717.369031.30230.500@commodore.email-scan.com \
    --to=mrsam-w1w4qow4midglshwzvccbg@public.gmane.org \
    --cc=chris-FSXMH2gLahXJKwlM9GxbOw@public.gmane.org \
    --cc=dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org \
    --cc=davidel-AhlLAIvw+VEjIGhXcJzhZg@public.gmane.org \
    --cc=davids-Rrbileazn+l54TAoqtyWWQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox