| 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: <20070206.131631.82049180.davem@davemloft.net> Date: Tue, 06 Feb 2007 13:16:31 -0800 (PST) From: David Miller <davem@...emloft.net> To: torvalds@...ux-foundation.org Cc: kent.overstreet@...il.com, davidel@...ilserver.org, zach.brown@...cle.com, mingo@...e.hu, linux-kernel@...r.kernel.org, linux-aio@...ck.org, suparna@...ibm.com, bcrl@...ck.org Subject: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling From: Linus Torvalds <torvalds@...ux-foundation.org> Date: Tue, 6 Feb 2007 12:46:11 -0800 (PST) > And for user space, it means that we pass the _one_ thing around that we > need for both identifying the async operation to the kernel (the "cookie") > for wait or cancel, and the place where we expect the return value to be > found (which in turn can _easily_ represent a whole "struct aiocb *", > since the return value obviously has to be embedded in there anyway). I really think that Evgeniy's kevent is a good event notification mechanism for anything, including AIO. Events are events, applications want a centralized way to receive and process them. It's already implemented, and if there are tangible problems with it, Evgeniy has been excellent at responding to criticism and implementing suggested changes to the interfaces. - 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