Make epoll-multiplexer thread safe

[attila-lendvai]

Instead of a preallocated slot use WITH-FOREIGN-OBJECT to allocate
the events array, and thus make HARVEST-EVENTS safe for concurrent calls.

[attila-lendvai]

@sionescu, what's the deal with this? shall i rebase it? will you merge it?

i need it in our production systems and it's a headache to keep it in sync with master.

[attila-lendvai]

@sionescu any decision on this? do you theoretically agree to this?

i understand if you have no time to deal with it right now. i just want to know what to expect in the future, because we need to maintain a separate repo for this single patch to build our production systems (as opposed to simply getting iolib from quicklisp).

[attila-lendvai]

i had to rebase this, it should merge fine into the current master.

[darabi]

Hi @sionescu,

as a hu.dwim.web-server user, I'm also interested in this patch.
Will it be merged some time soon or should it be implemented differently?

Thank you

[attila-lendvai]

@sionescu i'm still maintaining this several years later, but it's quite a straightforward patch: it just moves the allocation of the buffer to the thread instead of a shared slot on the object. and i doubt it has serious performance implications.

any reason this is still not merged?

this was needed to fix an actually manifesting bug in our webapps.