Hi Vlad:
Thanks for your answer, if use current open sips LT mode, you are right,
because we del the fd from epoll every time once we get a trigger, but it is
not efficient to move in and move out fd every time, so if I want to use ET
mode and keep the tcp read socket in epoll, how about this case?
At 2011-12-05 18:53:24,"Vlad Paiu" <[email protected]> wrote:
Hello,
The scenario you are describing is not possible because the TCP connection has
attached to it the actual SIP msg that has been read so far. So if one worker
receives EAGAIN, it will put the TCP connection back on the IN reactor, and
when the FD will be triggered again, another worker will continue to read to
the same SIP msg as the previous worker.
Regards,
Vlad Paiu
OpenSIPS Developer
On 12/05/2011 05:16 AM, dongwflj wrote:
Hi:
I am learning opensip2, it seems currently no support for epoll ET, will we
support it in future?
If we use ET, two TCP sip messages come to server, I think one worker thread
should read all but till EAGAIN, but during the worker thread is reading,
another new packet coming on the same connection, that will trigger another
worker thread start to read buffer, will it cause the 2 worker thread read
wrong data? How can we solve this kind of problem? Thanks!
_______________________________________________
Users mailing list
[email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
