| 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
| ||
|
Message-ID: <f2b55d220702221342n5d712f16hfe689ee837b3516d@mail.gmail.com> Date: Thu, 22 Feb 2007 13:42:04 -0800 From: "Michael K. Edwards" <medwards.linux@...il.com> To: "Ingo Molnar" <mingo@...e.hu> Cc: "David Miller" <davem@...emloft.net>, johnpol@....mipt.ru, arjan@...radead.org, drepper@...hat.com, linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, hch@...radead.org, akpm@....com.au, alan@...rguk.ukuu.org.uk, zach.brown@...cle.com, suparna@...ibm.com, davidel@...ilserver.org, jens.axboe@...cle.com, tglx@...utronix.de Subject: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3 On 2/22/07, Ingo Molnar <mingo@...e.hu> wrote: > Secondly, even assuming lots of pending requests/async-threads and a > naive queueing model, an open request will eat up resources on the > server no matter what. Another fundamental misconception. Kernel AIO is not for servers. One programmer in a hundred is working on a server codebase, and one in a thousand dares to touch server plumbing. Kernel AIO is for clients, especially when mated to GUIs with an event delivery mechanism. Ask yourself why the one and only thing that Windows NT has ever gotten right about networking is I/O completion ports. Cheers, - Michael - 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/
Powered by blists - more mailing lists