linux-kernel - Re: considering kevent - the kernel development process

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: <45F705EE.6040405@argo.co.il>
Date:	Tue, 13 Mar 2007 22:13:34 +0200
From:	Avi Kivity <avi@...o.co.il>
To:	Christoph Hellwig <hch@...radead.org>,
	Johann Borck <johann.borck@...sedata.com>,
	linux-kernel@...r.kernel.org
Subject: Re: considering kevent - the kernel development process

Christoph Hellwig wrote:
> It's not obvious, but utter bullshit.  Please go away if you think
> starting post with quotes from CGL specs is even remotely close to
> a good idea.
>   

I don't know about CGL, but a unified async notification mechanism _is_ 
needed.  In ~2002, I needed one, and what I ended up with was a Red Hat 
2.4 kernel with IO_CMD_POLL hacked in.  Five years later, mainline still 
can't do that.

Whether it's syslets, threadlets, io_getevents with networking support, 
kevents, epoll with kaio support, queued signals, or something else, 
users don't care, but they need _something_.  Please don't ignore the 
users just because they quote the wrong text.  The need is very real.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

-
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/