netdev - Re: 200 millisecond timeouts in TCP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <D439C073-B9B9-4C09-8A6A-F0FDD325DAAB@earthlink.net>
Date:	Thu, 3 Jun 2010 15:51:43 -0700
From:	Mitchell Erblich <erblichs@...thlink.net>
To:	Ivan Novick <novickivan@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: 200 millisecond timeouts in TCP


On Jun 3, 2010, at 3:37 PM, Ivan Novick wrote:

> Hello,
> 
> Using tcpdump and systemtap I am seeing that sometimes retransmission
> of data is sent after waiting 200 milliseconds.  However sometimes
> retransmissions happen quicker.
> 
> Is there a specifc event that causes these 200 milisec delays to kick
> in?  Are those events identifiable in netstat -s output?
> 
> Also do you know if the timeout numbers for TCP are configurable parameters?
> 
> I am testing on RHEL5 with this kernel: 2.6.18-164.15.1.el5.
> 
> Cheers,
> Ivan Novick
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Ivan Novick,

There is a public Linux TCP paper that I think covers this.

Mitchell Erblich--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html