What is tw at /proc/net/sockstat?!

Hi everybody~!
I just want to know tw at /proc/net/sockstat ...!!

In my server
--------------------------------------------------------------------------------------------
~$cat /proc/net/sockstat
sockets: used 108
TCP: inuse 38 orphan 0 tw 100 alloc 38 mem 23
UDP: inuse 5
RAW: inuse 3
FRAG: inuse 0 memory 0
--------------------------------------------------------------------------------------------

Thank you for reading this topic~!
and please anwer if you know..

(E-Mail Removed) wrote:

> Hi everybody~!
> I just want to know tw at /proc/net/sockstat ...!!
>
> In my server
> ------------------------------------------------------
> ~$cat /proc/net/sockstat
> sockets: used 108
> TCP: inuse 38 orphan 0 tw 100 alloc 38 mem 23
> UDP: inuse 5
> RAW: inuse 3
> FRAG: inuse 0 memory 0
> ------------------------------------------------------

cf. /usr/src/linux/net/ipv4/proc.c

tw stands for TIME-WAIT

TIME-WAIT - represents waiting for enough time to pass to be sure
the remote TCP received the acknowledgment of its connection
termination request.

Spoon <root@127.0.0.1> wrote:
> tw stands for TIME-WAIT

> TIME-WAIT - represents waiting for enough time to pass to be sure
> the remote TCP received the acknowledgment of its connection
> termination request.

Interesting description. I was always under the impression that it
was there to preserve connection state long-enough to be confident
(statistically certain) that all segments of the connection that may
have wandered-off into seedy corners of the network had timed-out
before a new connection of the same name was started. Hence the
reason it is described as being a multiple of the MSL Maximum Segment
Lifetime.

rick jones
--
firebug n, the idiot who tosses a lit cigarette out his car window
these opinions are mine, all mine; HP might not want them anyway...
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...

Rick Jones wrote:

> Spoon wrote:
>
>> tw stands for TIME-WAIT
>>
>> TIME-WAIT - represents waiting for enough time to pass to be sure
>> the remote TCP received the acknowledgment of its connection
>> termination request.
>
>
> Interesting description. I was always under the impression that it
> was there to preserve connection state long-enough to be confident
> (statistically certain) that all segments of the connection that may
> have wandered-off into seedy corners of the network had timed-out
> before a new connection of the same name was started. Hence the
> reason it is described as being a multiple of the MSL Maximum Segment
> Lifetime.

I read that definition in RFC 793
http://www.rfc-editor.org/rfc/rfc793.txt
(which is almost 25-years old)