route entry and tcp_usr_connect/tcp_connect
dillon at apollo.backplane.com
Fri Feb 8 09:30:07 PST 2008
:It turns out the previous problem (tcp_timer_2msl) is related to
:calling tcp_output() in tcp_usr_connect() and tcp_connect().
:For TCP PRU_CONNECT is handled on tcp_thread following two
:functions are executed in _that_ thread:
:tcp_connect() and tcp_output()
:So I made following patch:
:- If target port is not tcp_thread's port, then we free the route
:entry allocated by in_pcbladdr().
:- In tcp_usr_connect(), if target port is not tcp_thread's port, we
:dispatch tcp_output to the target port to be called.
:Please review it:
I like it. We should probably also start adding cpu-assertions to the
tcp protocol stack, as a step towards removing the BGL from the protocol
<dillon at backplane.com>
More information about the Submit