linux-kernel - Re: Syslets, Threadlets, generic AIO support, v6

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: <20070530132030.GA22330@elte.hu>
Date:	Wed, 30 May 2007 15:20:30 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Zach Brown <zach.brown@...cle.com>, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@....com.au>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Ulrich Drepper <drepper@...hat.com>,
	Evgeniy Polyakov <johnpol@....mipt.ru>,
	"David S. Miller" <davem@...emloft.net>,
	Suparna Bhattacharya <suparna@...ibm.com>,
	Davide Libenzi <davidel@...ilserver.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Syslets, Threadlets, generic AIO support, v6

* Ingo Molnar <mingo@...e.hu> wrote:

> epoll is very much is capable of doing it - but why bother if 
> something more flexible than a ring can be used and the performance 
> difference is negligible? (Read my other reply in this thread for 
> further points.)

in particular i'd like to (re-)stress this point:

 Thirdly, our main problem was not the structure of epoll, our main
 problem was that event APIs were not widely available, so applications
 couldnt go to a pure event based design - they always had to handle
 certain types of event domains specially, due to lack of coverage. The
 latest epoll patches largely address that. This was a huge barrier
 against adoption of epoll.

starting with putting limits into the design by going to over-smart data 
structures like rings is just stupid. Lets fix, enhance and speed up 
what we have now (epoll) so that it becomes ubiquitous, and _then_ we 
can extend epoll to maybe fill events into rings. We should have our 
priorities right and should stop rewriting the whole world, especially 
when it comes to user APIs. Right now we have _no_ event API with 
complete coverage, and that's far more of a problem than the actual 
micro-structure of the API.

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