xxx_poll callbacks and multiple event loops

Marc Lehmann schmorp at
Tue Nov 8 18:39:19 CET 2011

On Mon, Nov 07, 2011 at 12:01:13PM +0000, Paddy Byers <paddy.byers at> wrote:
> (Unlike my last attempt) this can now run two node instances in separate
> threads, each running a file io benchmark and the responses are being
> directed to the correct threads for processing.
> Does this make sense or am I missing something?

It breaks the API and makes everything slower than it could be, all
because node.js wants to do its own software cpu thing :)

I think my proposal is far simpler, and doesn't run the risk of breaking
the logic inside libeio (such as request/thread counting, stuff such as
matime/maxreqs and so on). It's possible that it happens to work, but I don't
really want to think through all cases.

If node.js really wants to go head-through-wall, then I think having the
extra thread sending requests to event loops is far simplar and safer.

                The choice of a       Deliantra, the free code+content MORPG
      -----==-     _GNU_    
      ----==-- _       generation
      ---==---(_)__  __ ____  __      Marc Lehmann
      --==---/ / _ \/ // /\ \/ /      schmorp at
      -=====/_/_//_/\_,_/ /_/\_\

More information about the libev mailing list