[reSIProcate] epoll prototype patch
Adam Roach
adam at nostrum.com
Tue Nov 16 19:46:10 CST 2010
On 11/16/10 19:12, Nov 16, Francis Joanis wrote:
> Do we know if the current build scripts are all still in use and
> working (I mean all the targets and options - I mainly only use the
> core ones myself)? If it turns out only a subset of them are really
> required it will probably not be a huge task to port the build system
> to something like CMake.
Yes, by and large, they are. I just took a quick scan through the
options that the configuration script takes care of. For each option in
the small handful that I don't use myself, I can easily identify someone
who does.
There may be a bit of cruft in the files in the build directory -- for
example, the old and deprecated "armcross" target and the now unused
"LNDIR" stuff -- but I think most of the contents of that directory are
pretty much in use nowadays.
> As for using libevent directly in reSIProcate, this could be very
> interesting (since it looks like it is already doing the best event
> "selection" abstractions per OS). We would need to see if it would
> easily integrate within the threading model of the SipStack (I'm
> thinking process/buildFdSet).
I haven't looked at the epoll patch, but I imagine that whatever
technique Kennard has used should for epoll should translate pretty
directly into libevent.
That said, when I took a look at doing exactly this (several years ago),
I concluded that doing it in a clean fashion that takes full advantage
of an event model would be fairly major surgery.
/a
More information about the resiprocate-devel
mailing list