| 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
| ||
|
Date: Sat, 29 Jul 2006 13:54:51 -0700 From: Nicholas Miell <nmiell@...cast.net> To: Evgeniy Polyakov <johnpol@....mipt.ru> Cc: Ulrich Drepper <drepper@...hat.com>, Zach Brown <zach.brown@...cle.com>, David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [RFC 1/4] kevent: core files. On Sat, 2006-07-29 at 19:48 +0400, Evgeniy Polyakov wrote: > On Fri, Jul 28, 2006 at 09:32:42PM -0700, Nicholas Miell (nmiell@...cast.net) wrote: > > Speaking of API design choices, I saw your OLS paper and was wondering > > if you were familiar with the Solaris port APIs* and, if so, you could > > please comment on how your proposed event channels are different/better. > > As far as it concerns kevents - userspace "ports" are just usual users > of kevents, like timer notifications. Add another syscall to "complete" > requested kevents and you get exactly Solaris ports. > It is fairly simple to implement on top of kevents, I just do not see > immediate benefits from that. > Sorry, I wasn't talking about kevent, I was talking about the interfaces described in "The Need for Asynchronous, Zero-Copy Network I/O" by Ulrich Drepper -- specifically the ec_t type and related functions and the modifications to struct sigevent. -- Nicholas Miell <nmiell@...cast.net> - 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