linux-kernel - Re: [patch 14/22] pollfs: pollable futex

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] [day] [month] [year] [list]

Message-ID: <a36005b50705062246x21d8c3aah9db53b1e0bf4f79a@mail.gmail.com>
Date:	Sun, 6 May 2007 22:46:02 -0700
From:	"Ulrich Drepper" <drepper@...il.com>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	"Davide Libenzi" <davidel@...ilserver.org>,
	"Davi Arnaut" <davi@...ent.com.br>,
	"Eric Dumazet" <dada1@...mosbay.com>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [patch 14/22] pollfs: pollable futex

On 5/6/07, Andrew Morton <akpm@...ux-foundation.org> wrote:
> What is your position on the timerfd/signalfd/etc patches?

One more thing: recently in a network-related discussion with DaveM
et.al. we came across a situation where we want events from the
kernel.  The requirement is for fast event notification (or
non-blocking polling) and the event is only implicitly needed.  Having
a file descriptor open is not an option.  The possibilities are

- open a file in /proc or /sys or a socket for every call to te
function to check for events

- have a memory-mapped interface like kevent which does not keep file
descriptors open

File descriptions are problematic when it comes implicitly uses in the
runtime.  This is, for instance, why we have MAP_ANON instead of
keeping a /dev/null file descriptor open all the time.
-
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/