event engine library selection

Poul-Henning Kamp phk at phk.freebsd.dk
Tue Mar 14 12:33:22 CET 2006

In message <ujrr755ff9q.fsf at cat.linpro.no>, Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= writes:

>It also has several features the ISC code lacks, like support for
>signals, kqueue, poll etc.

yeah, well, and vice versa, the ISC code has a lot of high-level stuff
that provos code lacks.

>> If we decide on the Provos engine, we may have to spend time to fix up his
>> multi-thread support and hope he will accept the patches.
>He's a reasonable guy, I don't see any reason why he wouldn't.  In any
>case, we'll want to keep our own copy of the code in our tree.

Lets go with provos code then.

Integrating it in the tree probably takes a bit more auto* foo than I
have, since I guess we need to merge libevent's auto* stuff into our
auto* stuff ?

When I compile libevent on -current I run into weird messages because
<sys/event.h> includes <sys/_lock.h> to cope with various userland
malware.  I'm investigating right now what malware that might be.

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

More information about the varnish-dev mailing list