From: Andreas Voellmy <andreas.voel...@gmail.com> Subject: Re: I/O manager: relying solely upon kqueue is not a safe way to go Date: Sat, 16 Mar 2013 11:08:40 -0400
> A better approach would be to try to register with kqueue and then if it > doesn't work, register it with an IO manager thread that is using select > for the backend. We can probably reuse the IO manager thread that is > watching timers for this purpose. With the parallel IO manager, we no > longer use it to wait on files, but we certainly could do that. That would > save us from adding more threads. By only failing over to the > manager-thread-using-select-backend if kqueue fails, we don't need to > maintain a list of files types that kqueue works for, which might be a pain > to maintain reliably. Yeah, I think that is the best approach. _______________________________________________________ - PHO - http://cielonegro.org/ OpenPGP public key: 1024D/1A86EF72 Fpr: 5F3E 5B5F 535C CE27 8254 4D1A 14E7 9CA7 1A86 EF72
pgptMo4XEG6Dl.pgp
Description: PGP signature
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
