site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com You are totally right. I'm probably overthinking this, but I haven't seen much detailed information on kqueue:s on Google, books and elsewhere and I didn't want to spend unnecessary time implementing something bound to fail. <http://people.freebsd.org/~jlemon/papers/kqueue_freenix.pdf> -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... On Apr 7, 2009, at 2:47 AM, Påhl Melin <listor.pm@gmail.com> wrote: 2009/4/6 A.M. <agentm@themactionfaction.com>: On Apr 6, 2009, at 7:12 AM, Påhl Melin wrote: I would expect the kqueue not to be filled up with EVFILT_READ and EVFILT_WRITE events, but to have only one of each whenever the buffers are "ready". But the question is if I'm guaranteed to have alternating read and write events? Or if I get starvation of any kind? I don't see anything about this matter in the man pages so I'm curious if it's specified at all? There are no guarantees made, but in my usage, I have not experienced starvation under conditions similar to yours. You may be overthinking this. Just try it and you can address starvation later, if it occurs. There are also 14 other papers referencing that one, which discuss things like a Linux implementation. A useful search engine network to bookmark for CS papers is Citeseer: <http://citeseer.ist.psu.edu

. This email sent to site_archiver@lists.apple.com