Gregory Nutt
|
04ad162540
|
Networking: Clean up some naming that has bothered me for a long time... There are no interrupts and no interrupt handlers in the network. There are events and event handler (there used to to be interrupt logic in there years ago but that is long, long gone).
|
2017-08-29 14:08:04 -06:00 |
|
Gregory Nutt
|
171d183e8e
|
Networking: A placeholder for some missing logic in the previous change related to monitoring network status for dup'ed sockets. If one of the dup'ed socket's is closed, then network monitor resources associated with that one socket must be recovered. Also, in the event that socket is being used on one thread, but then closed on another, any threads waiting for events from the socket should be informed of the closure. That latter requirement is not implemented because current data structures do not support it.
|
2017-08-29 13:24:49 -06:00 |
|
Gregory Nutt
|
0f7a52bc28
|
Networking: Fix a runaway recursion problem introduced the previous fixe for shutting down dup'ed sockets.
|
2017-08-29 12:27:58 -06:00 |
|
Gregory Nutt
|
d40ee8e79d
|
Networking: Start the network monitor for a socket when a TCP socket is dup'ed.
|
2017-08-29 10:53:04 -06:00 |
|
Gregory Nutt
|
9db65dea78
|
Networking: TCP disconnection callbacks are not retained in a list. This will support mutiple callbacks per lower-level TCP connection structure. That is necessary for the cae where a socket is dup'ed and shares the same lower-level connection structure. NOTE: There still needs to be a call to tcp_start_monitor() when the socket is dup'ed.
|
2017-08-29 10:38:01 -06:00 |
|
Gregory Nutt
|
92f44c5607
|
Networking: Move net/inet/net_monitor.c to net/tcp/tcp_monitor.c in preparation for design change to fix monitoring of duplicated sockets.
|
2017-08-29 08:40:13 -06:00 |
|