linux-kernel - epoll optimizations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4981C648.3000108@symas.com>
Date:	Thu, 29 Jan 2009 07:07:52 -0800
From:	Howard Chu <hyc@...as.com>
To:	Davide Libenzi <davidel@...ilserver.org>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: epoll optimizations

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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/