I/O manager: relying solely upon kqueue is not a safe way to go

[PHO]

From: Andreas Voellmy <andreas.voellmy at gmail.com>
Subject: Re: I/O manager: relying solely upon kqueue is not a safe way to go
Date: Sat, 16 Mar 2013 10:29:26 -0400

> Note also that no implementations of kqueue
>> support monitoring writability of regular file writes, which also
>> endangers the current use of kqueue-based I/O manager namely
>> "threadWaitWrite".
>>
>
> Are you sure about this? Do you have any example program demonstrating
> this? I just took your kqueue-poll-select.cpp program and tested
> registering a file for a write event (i.e. changing EVFILT_READ to
> EVFILT_WRITE, POLLIN to POLLOUT, and use writefds rather than readfds) and
> it works fine on a file:

Sorry, I just read that in man pages in all platforms but it turned
out that most implementations actually supoprt that. Here's my updated
program:
https://gist.github.com/phonohawk/5169980#file-kqueue-poll-select-cpp

NetBSD 6.99.17 is the only platform that prohibits waiting on regular
file writes:
https://gist.github.com/phonohawk/5169980#file-x86_64-unknown-netbsd6-99-17-txt

_______________________________________________________
 - PHO -                         http://cielonegro.org/
OpenPGP public key: 1024D/1A86EF72
Fpr: 5F3E 5B5F 535C CE27 8254  4D1A 14E7 9CA7 1A86 EF72
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20130318/5fc4de6e/attachment.pgp>