David,
I believe you are right, it is possible to get into a dead lock between worker
A and B in the case where A is waiting for B and B is waiting for A.
We solved that by tail drop. Another way of doing that is by using a separate
handover worker from NAT worker.
We are exploring some new
*Hi Damjan*
*Thnaks for your answer,*
*I think it is possible (I encountered this problem) to have deadlock even when
I use separate CPU for handoff and NAT processing, Or same CPU with congestion
drop mechanism.*
*I studied the code and separate the CPUs of handoff and NAT processing, in
> On 29 Dec 2018, at 07:26, david.leitch@gmail.com wrote:
>
> Hi ...
>
> I know that we need handoff mechanism when running multithread because
> traffic for specific inside network user must be processed always on same
> thread in both directions and We can not remove handoff node from
Hi ...
I know that we need handoff mechanism when running multithread because traffic
for specific inside network user must be processed always on same thread in
both directions and We can not remove handoff node from NAT nodes ,because
handoff is faster than locking mechanism.
So the
