From: Howard Chu <hyc@symas.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: epoll optimizations
Date: Thu, 29 Jan 2009 07:07:52 -0800 [thread overview]
Message-ID: <4981C648.3000108@symas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703061628470.3661@alien.or.mcafeemobile.com>
Something I tripped over recently, that might be nice to change... HANGUP
events are always reported, and apparently can't be turned off. In
level-triggered mode, if your event loop treats Hangups as lower priority than
read/write events, an outstanding Hangup will continue to be signaled every
time you call epoll_wait() until it's finally disposed of. It would be nice if
Hangups were always oneshot events, regardless of whether the FD was
configured level, edge, or oneshot. Certainly we know that the *cause* of a
Hangup can only happen once on any descriptor, so it makes no sense for it to
be reported more than once.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
next prev parent reply other threads:[~2009-01-29 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 0:34 [patch 3/3] epoll optimizations and cleanups Davide Libenzi
2009-01-29 15:07 ` Howard Chu [this message]
2009-01-30 0:10 ` epoll optimizations 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=4981C648.3000108@symas.com \
--to=hyc@symas.com \
--cc=davidel@xmailserver.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox